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

[DonJayamanne]

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

[znd4]

I know you included etc., but I'd like to explicitly call out meta.yml, environment.yml, and maybe even anaconda-project.yml. :)

[wis]

also .pep8 and I think .pycodestyle

[DonJayamanne]

Luciana Abud (@luabud) we have an external PR for this issue.
FYI, this was meant to be an experiment, hence the label.
We might also want to list down each file that we want to support/look for.

[karthiknadig]

Don Jayamanne (@DonJayamanne) this is a change to package.json. Is there a way to add this to experiment?

[DonJayamanne]

Sorry, I missed that question.
I can see only one way of doing this.
When extension loads, we modify package.json file, then next time they load extension package.json file will contain the required changes and things will work as expected.

I.e. extension will need to modify package.json during runtime, instead of shipping it.

We might need to change how this experiment works, else we'll get telemetry for users who open VSC once and we'll (via telemetry) get notified they are in the experiment, when in fact they aren't (not until they re-load VS Code).