CPython and PyPy envs

[edgarrmondragon]

Hi folks!

I'm curious about #2089. There was a PR, but it was closed without being merged. Are there any workarounds to avoid name collisions of Poetry envs for CPython and PyPy implementations.

I was thinking of contributing a new config (e.g. virtualenvs.suffix, with default -py{minor}) to allow users to create both CPython and PyPy envs without introducing any breaking changes. This would be similar to virtualenvs.prompt in that it would be a template string that supports at least the following variables:

• minor, e.g. 3.9
• implementation , e.g. cpython

Users could distinguish envs with a new template:

$ poetry config virtualenvs.suffix '-{implementation}{minor}'
$ poetry env use pypy3.9
Using virtualenv: /path/to/poetry-eRuhADh4-pypy3.9
$ poetry env use python3.9
Using virtualenv: /path/to/poetry-eRuhADh4-cpython3.9