Consider adding more patterns to files.exclude

[pamelafox]

I find that I've been modifying files.exclude in my dev containers recently to exclude
ruff_cache, .coverage, pytest_cache, and .pyc files

I am wondering if you'd consider adding them to the default files.exclude, or if there's any other easy way for Python devs to easily exclude them (without having to learn glob syntax, which I must admit, I still haven't truly learnt).

[lramos15]

Maybe this is something the python extension wants to introduce, cc @brettcannon @isidorn .

No plans currently to add any to the core defaults.

[isidorn]

We could at least add this to the Python Profiles @luabud

[luabud]

Agree with adding it to the Python profile.
@brettcannon somewhat inspired by https://github.com/github/gitignore/blob/main/Python.gitignore, I wonder if it'd make sense to add these to files.exclude in our Python profile?

__pycache__/
htmlcov/
.tox/
.nox/
.coverage
.coverage.*
.cache
coverage.xml
*.cover
*.py,cover
.hypothesis/
.pytest_cache/
cover/
.mypy_cache/
.ruff_cache/

[brettcannon]

It's seems rather broad (i.e., I don't know if all of those coverage-related ones are used by coverage.py), but otherwise the list seems reasonable.

[pamelafox]

I'm not sure I'd stick coverage.xml in there- even though I do typically gitignore it, I sometimes look at it (being an XML file, it's grokkable). I looked at one just last week. And if htmlcov is the HTML report, I'd also leave that off.

[luabud]

Noted. How about

__pycache__/
.tox/
.nox/
.coverage
.coverage.*
.cache
.hypothesis/
.pytest_cache/
.mypy_cache/
.ruff_cache/

[pamelafox]

That looks good, yes, assuming that .tox and .nox are correct, I haven't used those tools myself.

I just double checked .hypothesis/ and it doesn't look like a directory a human would want to peruse:

(.venv) hypothesis-test % ls .hypothesis 
examples	unicode_data
(.venv) hypothesis-test % ls .hypothesis/examples 
0dc35b04ae5fe0c5	3c054902db8ac259	40314c85a74cc041	9f95b08733d63e1e
(.venv) hypothesis-test % ls .hypothesis/unicode_data 
14.0.0
(.venv) hypothesis-test % ls .hypothesis/unicode_data/14.0.0 
charmap.json.gz
(.venv) hypothesis-test % ls .hypothesis/examples           
0dc35b04ae5fe0c5	3c054902db8ac259	40314c85a74cc041	9f95b08733d63e1e
(.venv) hypothesis-test % ls .hypothesis/examples/0dc35b04ae5fe0c5 
68e09c5bfbe3cdbe	bec021b4f368e306

(With each of the leaf files being binary data, not human readable)

So if you feel good about .tox/.nox, I think it's a good list.

[brettcannon]

assuming that .tox and .nox are correct, I haven't used those tools myself.

I can confirm both are correct for those tools.

[brettcannon]

Should I just transfer this issue over to the Python extension at this point if there's not going to be any updates on the core side?

[isidorn]

Yes, I think that makes most sense. Thanks Brett!

[luabud]

This has been done last month and should be included in the default Python profile in VS Code. To verify, click on the gear icon > Profiles > Import Profile... > Python > Create, and then gear icon > Profiles > Show Profiles Content... and open the settings.json file: