Keep linting/styling/etc modules separate from project

[sandy081]

From @BeyondEvil

I have multiple projects and use pipenv for them all.

They all use tox so that's present in the Pipfile:

[dev-packages]
tox = "*"

However, while developing I also use black, flake8 etc. to deal with styling and linting and VSC adds these "automagically" to the Pipfile. Which I don't want. Because they're not relevant to the actual project.

Any linting/styling that happens outside of VSC is handled by tox.

So VSC should be happy if the chosen linting- and styling tools are available globally.

[DonJayamanne]

Duplicate of #4922

[DonJayamanne]

@BeyondEvil

If you want to use your global tools, then you can update settings.json to provide the fully qualified paths to the global tools:
E.g.

"python.formatting.blackPath": "<fully qualified path to black executable>"

Hope this answers your question. More information can be found here https://code.visualstudio.com/docs/python/linting#_specific-linters