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
Managing dual 2.x and 3.0 installations on Windows #47886
Comments
I installed a 3.0 beta for the first time in Windows. I was surprised If you run "assoc .py" from a command line, the return value is So at least a warning in the installation instructions would be nice. Many thanks, by the way, to all the python developers over the years. |
This won't solve the problem of dual installations, but it'll leave things how you were expecting... There is an option in the installer on the customize page for "Register Extensions". Choosing to not install that item will keep the installer from modifying the path and file association. I think we could probably have a message on the installer to say that the "Register Extensions" feature would be overwriting your previous settings if it finds settings of a previous version. |
This seems like a normal file association fight, no different than not being able to have both IE and Firefox associated with .html files. bpo-2375 has been rejected, so I don't think it is a relevant superseder. I don't see how this is any different than having multiple 2.x installations and needing to pick the current one to work with. If 2.3 were the default and I tried to run a script with decorators I would end up with the same result. |
Now fixed thanks to PEP-397. http://docs.python.org/py3k/whatsnew/3.3.html#pep-397-python-launcher-for-windows |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: