That last part is important: the installation will have registered them as the applications to execute when Python is executed. Installing the 3.4.1 package will have put py.eye and pyw.exe launchers into %SYSTEMROOT% (on the Windows system PATH) and then associate those with. Specifically, remove the “Register Extensions” option from installing. Install it and, this time, do NOT accept the defaults.The defaults include not adding python.exe to the path.) At the time I write this, that would be 3.4.1 and 2.7.7. Let’s say you want to have the latest 3.x branch and 2.x branch installed at the same time. The documentation on this is sometimes tricky to wade through so I want to present what I hope is a simplified view here. The official solution for coexistence is the Python Launcher for Windows, talked about in PEP 397, which was included in Python 3.3.0. Here I’ll talk about how the Python development team has eased this with the Windows launcher. But, on Windows at least, this has been tricky in terms of having two Python versions installed and easily moving between them. ( See more details on this.) This often puts testers in the position of having to make Python solutions that run on both versions. There is currently a large gap in the Python world between the 2.x and 3.x branch. A lot of testers are on Windows machines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |