A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/108951.html below:

[Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstream

[Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstream [Python-Dev] [PEPs] Support the /usr/bin/python2 symlink upstreamGlenn Linderman v+python at g.nevcal.com
Tue Mar 8 03:33:12 CET 2011
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>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4