You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2020-09-21.16:26:25.259>created_at=<Date2020-09-18.00:40:16.557>labels= ['3.8', 'type-bug', 'expert-installation']
title='Warnings when installing Linter on VS code on Linux and Windows.'updated_at=<Date2020-09-21.16:26:25.258>user='https://bugs.python.org/zamunda'
nstalled VS code, installed Python extension and when it loaded a pop up showed "Linter is not available" or something like that. Press Install, choose linter or never show again options.
Pressed Install - and it loaded the code to install it. It installed some stuff but there are errors about Path or something. See in the screenshot.
I've never had such Warnings before.
When I installed Python (on my system Windows) I put a checkmark on Add to Path, so it's not the problem.
Then I moved to Linux hoping it will work better and without warnings. Same Warining there too.
I guess there is a problem with python3-pip or something.
This warning is coming from pip, and it's because it has detected that your system configuration doesn't match what many Python developers assume. Specifically, that you've configured PATH to include both Python and any package scripts you happen to install.
We don't recommend adding these to PATH on Windows for your default install, so it's safe to ignore these warnings (provided you use a tool like VS Code or "python -m ..." to launch the scripts).
However, if you need these for a particular environment, when you create a virtual environment and activate it, your current session settings will be updated to put them on PATH and you should not see this error.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: