If 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.py
• setup.cfg?
• tox.ini
• pyproject.toml
• pytest.ini
• requirements.txt
• test_requirements.txt
• .pylintrc
• .flake8
• __init__.py
• manage.py
• src/__init__.py
• tests/__init__.py
• meta.yml
• environment.yml
• anaconda-project.yml
• .pep8
• .pycodestyle

[brettcannon]

Thanks to @soneji for the PR and everyone else in constructively participating in the discussion! This will be out in our March release.

[brettcannon]

One thing to be aware of is we used to get complaints about being overly liberal with launching the extension by folks who happen to have Python scripts in their e.g. C++ code base who do nothing more than generate test data by running Python, and so they only edit Python code every couple of months and not every time they open a workspace.

Without discussing it with the team 😉 , my guess is we can probably consider files that very clearly delineate that a project is primarily Python-based (e.g. pyproject.toml), but we can’t do it for just any file that someone using Python for any reason may have (e.g. configuration files for linters which you might have set up for that one Python file you have).

So I think that would suggest we could consider:

• Pipfile
• setup.py
• requirements.txt
• manage.py for Django
• environment.yml for Anaconda (maybe; that file is not exclusive to Python, e.g. R projects use the same file for Anaconda so this might not work out)

We don’t need setup.cfg as that’s covered by setup.py and pyproject.toml (otherwise that file is useless). pyproject.toml also takes care of Poetry. And everything else doesn’t necessarily suggest the code base is oriented towards Python (e.g. SConstruct has the issue of being used by projects that are not necessarily Python-focused, and using Pylint just means you have some Python code).