Which environment detector should killpy support next?

[Tlaloc-Es]

killpy currently detects 11 environment types — venv, poetry, conda, pipx, pyenv, pipenv, hatch, uv, tox, plus Python caches and build artifacts. Detectors are small and self-contained (see CONTRIBUTING.md for how to add one), so the real question is not can we add more, but which ones actually matter on real machines. That's where you come in.

Some candidates that have come up:

• Bazel outputs (bazel-out/, bazel-bin/) — Python monorepos can accumulate many GB of stale build trees.
• Docker build cache — often the single biggest disk consumer on a dev machine; even surfacing its size (with a pointer to docker system prune) would help.
• Windows Store Python installs — a common source of orphaned interpreters that regular tooling never sees.
• node_modules (opt-in) — many Python projects ship a JS frontend; an explicit flag would cover the full-stack case without stepping on npkill's turf.
• Jupyter kernels — kernelspecs pointing at deleted environments linger forever in ~/.local/share/jupyter/kernels.
• direnv layouts — .direnv/ folders hold per-project virtualenvs that nothing else cleans up.
• virtualenvwrapper (~/.virtualenvs) — an older convention, but those machines have had the longest time to accumulate cruft.
• nox (.nox/) — same story as .tox, just a different runner.

How to weigh in:

• 👍 the comments for the detectors you'd actually use
• Comment with candidates not on the list — a one-line "what it is and where it lives on disk" is plenty
• Bonus points for a rough size estimate from your own machine (du -sh <path>)

No promises on order or timeline — this thread is how we decide what's worth building next.