I think things have calmed down enough that I think people understand the options being presented. That means it’s time to see what people think I should do with the PEP.
Below is a ranked choice poll I’m running for a week (until next Friday). The options run from “you’re wasting your time, Brett”, to “all the things!”, and various combinations in between. You will notice that if the PEP happens then I’m keeping .venv as a reasonable directory name suggestion for a virtual environment no matter what (but I will take out the changes to the stdlib as part of the PEP and make it a “MAY” suggestion). I’m also giving folks another chance on the Python API (like PEP 517) versus JSON-RPC for WSP as at least @pf_moore seemed taken aback by what that could mean, so I want to make sure people are making an informed decision here.
As a reminder:
- PEP 832: virtual environment discovery - #90 by brettcannon summarizes things
- PEP 832: virtual environment discovery - #108 by brettcannon has a table at the end about when various things come into play (and FYI
pyproject.tomlis WSP if that isn’t clear) - API for discovering environments for a project is the discussion about JSON-RPC versus a Python API for WSP
- A CLI for WSP is expected and is assumed to support a simple fallback workflow that uses a
.venvdirectory for scripting and AI model use
Do note that I am recording people’s votes as it does matter if all the workflow tool authors go a certain way. I also consider the poll results advisory and not binding.
With that all out of the way …
- Withdraw the PEP
.venvand.python-envs.venv,.python-envs, and WSP over JSON-RPC.venv,.python-envs, and WSP as a Python API.venvand WSP over JSON-RPC.venvand WSP as a Python API
[EDIT: added “reminder” bullet list which reiterated things already said elsewhere that came up in private discussion with others.]