Opened 8 years ago
Last modified 7 years ago
#5064 new defect
Add option to override ./configure'd virtualenv
|Reported by:||ayleph||Owned by:|
./configure searches for
virtualenv in the following order:
Once a match is found, the search terminates. If a user has both python2 and python3 installed, then the python3
virtualenv may be configured for use, even when
--with-python3 is not specified. This results in an error for users who intend to use (or need to use) python2.
In the case of Arch Linux,
virtualenv is the python3 package, and
virtualenv2 is the python2 package. When I run
./configure without specifying
--with-python3, the python3
virtualenv is configured even though I didn't intend to use python3. To fix this, I must manually edit Makefile as follows before running
-VIRTUALENV = virtualenv +VIRTUALENV = virtualenv2
Some options for how to deal with this come to mind.
./configure support interactive configuration? If so, we could consider searching for all
virtualenvs and then asking the user which one they want to use.
--with-virtualenv switch  could be extended to accept a path to the desired executable.
If distributions consistently use
virtualenv2 for python2 and use
virtualenv3) exclusively for python3, perhaps we could tie the selection of
virtualenv to the python version specified in configuration.
--with-virtualenv is a programmed option in
./configure, but it isn't shown in
./configure --help. See issue #5022.
Change History (3)
comment:1 by , 8 years ago
|Priority:||major → trivial|
comment:2 by , 8 years ago
|Milestone:||0.8.0 → 0.9.0|
Moving this to 0.9.0
comment:3 by , 7 years ago
This is a defect probably, but not important enough to delay this release. I'm removing this from the milestone.
It would be nice to be able to set the virtualenv command, I agree. I'll look into this for the release, but I think it's low priority comparatively.