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 settin
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
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:\Te
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 updat
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:\Temp>ftype python.fil
On Sat, Feb 15, 2014 at 10:25 PM, 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
>
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:\Temp>test.py 1 2 3
['C:\\Temp\\test.py']
This is
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
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 overw
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 install
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
11 matches
Mail list logo
