Open kapec94 opened 10 months ago
This creates a
python3.10
environment:$ virtualenv --clear aaa --try-first-with=/usr/bin/python3.10 -p /usr/bin/python3.8 created virtual environment CPython3.10.13.final.0-64 in 525ms
This is a bug, PR to fix it welcome.
Thanks. As it caused me to lose a few days of work (tox and poetry are affected, if there’s an ini file with the setting), I’ll try to tackle it over the next weeks.
Bernát Gábor @.***> schrieb am Mi. 25. Okt. 2023 um 17:38:
Assigned #2659 https://github.com/pypa/virtualenv/issues/2659 to @kapec94 https://github.com/kapec94.
— Reply to this email directly, view it on GitHub https://github.com/pypa/virtualenv/issues/2659#event-10769295243, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKOE4NWQHRHB7K3RF5JLYTYBEW77AVCNFSM6AAAAAA6PHH4FWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQG43DSMRZGUZDIMY . You are receiving this because you were assigned.Message ID: @.***>
+1
Issue
Describe what's the expected behaviour and what you're observing.
--try-first-with
(and correspondingtry_first_with
config var) is described as "try first these interpreters before starting the discovery".When using it, I observe a different behavior for it, depending on whether I use
--python
arg with a full interpreter path, or just a version specification.Running
virtualenv
version20.24.6
.This creates a
python3.8
environment:This creates a
python3.10
environment:The issue is that the behavior is different, and it's difficult to say what is the expected one. Documentation doesn't even mention the
try_first_with
config, nor does the help for the--python
arg.Environment
Provide at least:
pip list
of the host python wherevirtualenv
is installed:Tested in a clean virtualenv based on Python 3.10.
Output of the virtual environment creation
Make sure to run the creation with
-vvv --with-traceback
:For
-p
with version spec:For
-p
with full path: