Fix #2089: Make Python implementation type as part of the venv name. - #2402
Fix #2089: Make Python implementation type as part of the venv name.#2402PetterS wants to merge 2 commits into
Conversation
|
Does not yet work since the "-py" prefix is still hard-coded in a few more places in When the following command is performed: Poetry prints: So it creates the correct environment, but then still decides to use the old one. Will update the rest of the places. |
|
It now works for me locally with pypy, so this is something that can be discussed. |
|
I'll give it a shot :) |
|
@abn would be nice if we could discuss this. |
|
In principle the change looks good. How would this handle reuse of an existing environment for the project? |
|
Since this PR only affects the name of the directory for Python implementations other than CPython, I think it should be fine? |
|
@PetterS are you still interested in bringing it to Poetry? If so, please merge changes from master branch and resolve potential conflicts. Whats more, please include some documentation on that matter. |
|
I'm still interested in this but I don't have the time to rebase it right now. |
|
Yes, I think it would be useful. |
|
Well this patch does not apply anymore. It has been 2 years! perhaps it works now? Otherwise, it should be easier to set the environment name since the info is already fetched. |
|
It behaves exactly the same according to the code but yes, it should be much easier to implement this behavior now. |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Resolves: #2089. Now "pypy" is part of the venv name so that it can be used together with poetry. Virtualenvs using Cpython will not change names to ensure backwards compatibility.