classification
Title: Warnings when installing Linter on VS code on Linux and Windows.
Type: behavior Stage: resolved
Components: Installation Versions: Python 3.8
process
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: Marcus.Smith, admin2, dstufft, eric.smith, ncoghlan, paul.moore, pradyunsg, steve.dower, tim.golden, zach.ware, zamunda
Priority: normal Keywords:

Created on 2020-09-18 00:40 by zamunda, last changed 2020-09-21 16:26 by steve.dower. This issue is now closed.

Files
File name Uploaded Description Edit
93283029-5dfbc880-f7d8-11ea-8552-fa5ee1e1d924.png zamunda, 2020-09-18 00:40 Picture showing the Warning.
Messages (2)
msg377078 - (view) Author: zamunda (zamunda) Date: 2020-09-18 00:40
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.
msg377260 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2020-09-21 16:26
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.

If you need further help, please visit the pip repository at https://github.com/PyPA/pip
History
Date User Action Args
2020-09-21 16:26:25steve.dowersetstatus: open -> closed
resolution: third party
messages: + msg377260

stage: resolved
2020-09-18 00:50:57zamundasetnosy: + ncoghlan, dstufft, pradyunsg, Marcus.Smith
2020-09-18 00:50:10zamundasetnosy: + paul.moore, tim.golden, zach.ware, steve.dower, zamunda
2020-09-18 00:45:29zamundasetnosy: + eric.smith, admin2, - zamunda
2020-09-18 00:40:16zamundacreate