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.) Michael -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
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