Re: Install python 2 and 3 in the wrong order
On Sunday, 16 February 2014 08:13:14 UTC, Nagy László Zsolt wrote: Though I don't see anything in the ActiveState builds (which are all I've ever used) to handle the #! type selection of the desired version. Just got done updating my 2.7, replacing 3.2 with 3.3, and then having to edit my path to make 2.7 primary... No py.exe I need both 2.7 and 3.3. And apparently, py.exe does not work the way it should be. Is the following any help http://www.perlmonks.org/?node_id=998428 -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
On 16/02/2014 08:13, Nagy László Zsolt wrote: And apparently, py.exe does not work the way it should be. What does this mean? Have you raised an issue on the bug tracker? I would happily reinstall 3.3 to solve the problem, but before I do that I would like to check all other related settings. So that after I reinstall 3.3, I will exactly know what was happening. It might be a good idea to change the installer of the 2.x series to detect if 3.x is already installed, and handle assignments of py and pyw files gracefully. It might be a good idea but I can't see it happening as (at least as far as I'm concerned) 2.7 is past its sell by date. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
On 15/02/2014 11:25, Nagy László Zsolt wrote: From a cmd window: ftype python.file=C:\Windows\py.exe %1 %* ftype python.noconfile=C:\Windows\pyw.exe %1 %* There is a serious problem with this! Example code test.py: #!/usr/bin/env python3 import sys print(sys.argv) Test run: C:\Temptest.py 1 2 3 ['C:\\Temp\\test.py'] This is too bad! Can somebody tell me what would be the good setup for py.exe? Do I have to reinstall Python3 with all libs? :-s Nagy, are you still seeing this behaviour? Because my system, with the exact ftype confiiguration you're describing, behaves as you would expect. c:\Users\timassoc .py .py=Python.File c:\Users\timftype python.file python.file=C:\Windows\py.exe %1 %* c:\Users\timt.py 1 2 3 ['C:\\Users\\tim\\t.py', '1', '2', '3'] I have 2.7 3.3 installed (and about half a dozen other versions, too). TJG -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
I should emphasize that this is with the /same/ x.y version... Installing 3.3 when the previous was 3.2 won't overlay. Though I don't see anything in the ActiveState builds (which are all I've ever used) to handle the #! type selection of the desired version. Just got done updating my 2.7, replacing 3.2 with 3.3, and then having to edit my path to make 2.7 primary... No py.exe I need both 2.7 and 3.3. And apparently, py.exe does not work the way it should be. I would happily reinstall 3.3 to solve the problem, but before I do that I would like to check all other related settings. So that after I reinstall 3.3, I will exactly know what was happening. It might be a good idea to change the installer of the 2.x series to detect if 3.x is already installed, and handle assignments of py and pyw files gracefully. -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
From a cmd window: ftype python.file=C:\Windows\py.exe %1 %* ftype python.noconfile=C:\Windows\pyw.exe %1 %* There is a serious problem with this! Example code test.py: #!/usr/bin/env python3 import sys print(sys.argv) Test run: C:\Temptest.py 1 2 3 ['C:\\Temp\\test.py'] This is too bad! Can somebody tell me what would be the good setup for py.exe? Do I have to reinstall Python3 with all libs? :-s -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
On Sat, Feb 15, 2014 at 10:25 PM, Nagy László Zsolt gand...@shopzeus.com wrote: From a cmd window: ftype python.file=C:\Windows\py.exe %1 %* ftype python.noconfile=C:\Windows\pyw.exe %1 %* There is a serious problem with this! Example code test.py: #!/usr/bin/env python3 import sys print(sys.argv) Test run: C:\Temptest.py 1 2 3 ['C:\\Temp\\test.py'] Just because I have a distrust of Windows's command interpreter, what happens when you type: ftype python.file ? Does it echo back what you thought it had, or has %* been eaten? If the %* is missing, that would explain the loss of arguments. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
Just because I have a distrust of Windows's command interpreter, what happens when you type: ftype python.file ? Does it echo back what you thought it had, or has %* been eaten? If the %* is missing, that would explain the loss of arguments. Already tought of that: C:\Tempftype python.file python.file=C:\Windows\py.exe %1 %* C:\Temp Something else is going on. -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
On 13/02/2014 11:53, Nagy László Zsolt wrote: I have Python 3.3 installed on my Windows 7 x64 box. Today I had to install Python 2.7 for an older app of mine. Here is my problem: although #!/usr/bin/env python3 is given in the file and py -3 program works fine, apparently the installation of python 2 simply has overwritten my settings (e.g. assignment *.py files to py.exe). Question: is there a way to fix this? Or do I have to reinstall Python 3 from scratch? (It would be a pity, I have tons of third party modules installed for it...) From a cmd window: ftype python.file=C:\Windows\py.exe %1 %* ftype python.noconfile=C:\Windows\pyw.exe %1 %* TJG -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
From a cmd window: ftype python.file=C:\Windows\py.exe %1 %* ftype python.noconfile=C:\Windows\pyw.exe %1 %* TJG Thank you. It worked. Although I must note that it only works if you start the cmd.exe as administrator (under Windows 7). Is it the only thing that was possibly overwritten by the python 2 installer? -- https://mail.python.org/mailman/listinfo/python-list
Re: Install python 2 and 3 in the wrong order
On 13/02/2014 12:03, Nagy László Zsolt wrote: From a cmd window: ftype python.file=C:\Windows\py.exe %1 %* ftype python.noconfile=C:\Windows\pyw.exe %1 %* TJG Thank you. It worked. Although I must note that it only works if you start the cmd.exe as administrator (under Windows 7). Is it the only thing that was possibly overwritten by the python 2 installer? Probably: things like .dlls are Python-2 specific. And the registry entries are per-version as well. TJG -- https://mail.python.org/mailman/listinfo/python-list
