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
Hi there!
I'm a PM for Python in VS Code, and I notice some of the Python extension's python.linting and python.formatting settings are being used in this repo's devcontainer.json file. These settings have been deprecated as in the latest Python extension pre-release version, as we're migrating our tooling support to extensions (see here for more details).
Because pylint is enabled for this repository, one workaround could be to include the new Pylint extension maintained by our team, and set the appropriate settings to use the pylint executable from the container itself. For example:
Alternatively, the path and importStrategy settings could be omitted so the pylint executable that is shipped with the Pylint extension is used instead (this approach would allow pylint to run faster than the one proposed above).
Description
Hi there!
I'm a PM for Python in VS Code, and I notice some of the Python extension's
python.linting
andpython.formatting
settings are being used in this repo's devcontainer.json file. These settings have been deprecated as in the latest Python extension pre-release version, as we're migrating our tooling support to extensions (see here for more details).Because pylint is enabled for this repository, one workaround could be to include the new Pylint extension maintained by our team, and set the appropriate settings to use the pylint executable from the container itself. For example:
Alternatively, the
path
andimportStrategy
settings could be omitted so the pylint executable that is shipped with the Pylint extension is used instead (this approach would allow pylint to run faster than the one proposed above).References
Thanks!
The text was updated successfully, but these errors were encountered: