Detect tox venvs

[f3flight]

Is your feature request related to a problem? Please describe.

Many projects use tox to create venvs and run tests, etc. There's a plugin for tox called tox-pdm which allows using pdm to install deps (to leverage pdm.lock, for example, i.e. for reproducible builds) This is all great but the end user still cannot use pdm directly without either

• creating yet another venv (.venv by default), which also requires setting up Python correctly (tox may have different Python binary set up)
• or activating one of venvs in .tox folder (but that doesn't allow managing them via pdm venv command)

It would be great if pdm could see and manage venvs created by tox, or maybe even more generally, and venvs in the subfolders of the current project, and allow using them for commands such as "pdm lock" etc, including use by default.

Describe the solution you'd like

I see a few options:

• pdm autodetects venvs inside ".tox" folder (or just searches for pyenv.cfg in all folders under project root and one folder down) - they show up in "pdm venv list" and can be used like any other venvs created by pdm
• pdm option "venv.location" can find tox venvs if pointed to ".tox" - right now it expects certain folder names and ignores others - maybe a new option to disable/change name expectations, like "venv.simple_names = True"
• new pdm option "venv.tox_working_dir = .tox" which will detect and allow using tox venvs

[frostming]

This should be done in the plugin and contribution is welcomed

[f3flight]

Hi @frostming , no problem, could you you point me to some doc or example plugin? I'll have a look

[frostming]

I think pdm-vscode is a simple example to demonstrate how to develop a plugin. And the docs are here: https://pdm.fming.dev/latest/plugin/write/