gladman added the comment:
I have now got it working using the command line:
C:\Program Files\Python35\Tools\scriptsC:\Program Files\Python34\python
2to3.py --help
I am not sure why the default Windows invocation of Python doesn't work with
2to3 as this works fine with other python scripts
New submission from gladman:
when I try to use the 2to3 script on the command line on Windows x64, I get the
response:
C:\Program Files\Python34\Tools\scripts2to3
C:\Users\brian\Downloads\puzzles.py
At least one file or directory argument required.
Use --help to show usage.
When I ask
Steve Dower added the comment:
If this occurs in 3.5 then it needs to be fixed (though I thought I'd already
fixed it once...).
I'll take a look.
--
assignee: - steve.dower
status: closed - open
versions: +Python 3.5, Python 3.6 -Python 3.4
___
gladman added the comment:
Thanks for the explanation. My apologies for this posting, which I will now
close
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24843
___
eryksun added the comment:
Your .py file association isn't configured to pass command-line arguments.
Revert to using the Python.File type that was created by Python's installer.
The associated command should be something like
C:\Windows\py.exe %1 %*
depending on where py.exe is
gladman added the comment:
Hi Steve,
The behaviour I reported was the same on Python 3.4 and 3.5rc1. But eryksun
was correct in suggesting that this was a problem in the way my file
association for Python was set up. My py_auto_file association was set to:
C:\Program
Changes by eryksun eryk...@gmail.com:
--
resolution: - not a bug
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24843
___
Steve Dower added the comment:
Yes, I see. Thanks for clarifying, it seems all the installers are fine but
Windows will generate associations that don't forward arguments.
--
assignee: steve.dower -
resolution: - not a bug
status: open - closed
versions: -Python 3.5, Python 3.6
Steve Dower added the comment:
I'm afraid there's no easy way to revert it. I may get to invest the time for
3.6's launcher[1] to make it available in Default Programs, but I've always
struggled to get that to work properly.
Explorer should always use the per-user command if it's there, and
eryksun added the comment:
My py_auto_file association
Oh, it's that auto filetype again. Steve, when you say you fixed this for 3.5,
does that means there's a simple command or API to revert this automatic ProgId
back to the Python.File type? This problem shows up repeatedly on Stack
Changes by eryksun eryk...@gmail.com:
--
versions: +Python 3.4 -Python 3.5, Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24843
___
___
11 matches
Mail list logo
