New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The -p N.M shortcut doesn't work for Python 3.5 on Windows #864
Comments
+1, never even knew that was a thing. If we want to do it nicely, probably want a patch logging it's deprecated when that is used for next release, and a deprecation note in the dev rel notes. |
IIRC, it's a thing because I added it because I was too lazy to type in the full interpreter. Then I never actually used it. Go figure. Yeah, I'll see if I can work up a proper deprecation note. For now, I mainly raised the issue so we had somewhere that said "it's broken and not going to get fixed" to justify me skipping the test I just added for the feature :-) |
@asottile - this is actually important for your |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions. |
The
--python
command line can take an abbreviated interpreter name. On Unix this is one of the versioned alias names (python2.7
,python3
, ...) and is looked up onPATH
.On Windows the versioned names don't exist so the registry is searched for the Python version specified. So,
-p 2.7
finds the location of Python 2.7 in the registry and uses that.However, the registry layout is not well documented, and is complex (user installs, 32-bit vs 64-bit). It also seems to have changed in Python 3.5, and
-p 3.5
does not work. Rather than attempt to fix this, though, I propose that the feature be marked as deprecated, and left as it stands. It's not clear that it was ever widely used.People wanting to use an abbreviated interpreter name would be better to run
py -N.M -m virtualenv
(assuming virtualenv is installed under Python N.M) orpy -N.M C:\path\to\virtualenv
to run a standalone copy of virtualenv. This uses the (fully supported) Python launcher to select the required Python version.The text was updated successfully, but these errors were encountered: