Ask questionsIf I have Python-related files in my workspace, automatically activate the extension

Goal - Lets not wait for the user to open a python file to activate the extension

If the user has some of the following files we could probably activate the extension without having to wait for the user to open a python file:

  • pip env files
  • poetry files
  • setup.cfg?
  • tox.ini
  • pyproject.toml
  • pytest.ini
  • requirements.txt
  • test_requirements.txt
  • .pylintrc
  • .flake8
  • src/
  • tests/
  • meta.yml
  • environment.yml
  • anaconda-project.yml
  • .pep8
  • .pycodestyle

Answer questions luabud

@ericsnowcurrently Let's start with pyproject.toml first to be conservative, then we can add as if we don't receive complaints.


Related questions

Auto Scroll in the Jupyter output hot 3
Workspace contains pipfile but pipenv --venv failed hot 2
Can you turn off the Microsoft Python Language Server? hot 2
Unable to debug Python tests (duplicate entries in "env") hot 2
Jupyter server crashed. Unable to connect. Cannot assign requested address hot 2
Auto Scroll in the Jupyter output hot 2
Unable to run launch targets with newest VS Code Python extension hot 2
Unable to start jupyter python interactive window hot 1
HBox output is not shown correctly in the interactive window hot 1
Debug -> Add Debug Configuration 'Cannot read property openConfigFile' hot 1
VSCode cannot connect to jupyter server; with browser this works fine hot 1
Linux arm64/aarch64 support hot 1
Add setting to disable icon for "Run Python File In Terminal" hot 1
Extension Host keeps crashing hot 1
Activate environment before debugging tests hot 1
Github User Rank List