[Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstream
Glenn Linderman
v+python at g.nevcal.com
Tue Mar 8 03:33:12 CET 2011
More information about the Python-Dev mailing list
Tue Mar 8 03:33:12 CET 2011
- Previous message: [Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstream
- Next message: [Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstream
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/7/2011 4:00 PM, Michael Foord wrote: > On 07/03/2011 23:52, Greg Ewing wrote: >> Michael Foord wrote: >> >>> - I doubt calling it python.exe will fly, but I'm not sure. If >>> so what will you call what is currently 'python.exe'? - if not then >>> "python foo.py" on the command line will *still* not work... >> >> However, if it's installed as the exe associated with the .py >> and .pyw extensions, then simply 'foo.py' on the command line >> *will* work, and will work better than it does now. >> > So long as '.py' and '.pyw' are set in the PATHEXT environment > variable. (Which again the Python installer doesn't do by default.) No, PATHEXT only means you can invoke foo.py and foo and get the same results (sometimes, depending on what all in on PATH and PATHEXT) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20110307/86bdc477/attachment.html>
- Previous message: [Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstream
- Next message: [Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstream
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list