try-first-with
behaves differently for --python
full paths and version specs
#2659
Labels
try-first-with
behaves differently for --python
full paths and version specs
#2659
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:The text was updated successfully, but these errors were encountered: