> A cleaner (though still dirty) way to achieve this would be to add a > link to the appropriate "python.exe" in a directory already on the path > such as c:\Windows\system32 That would be fairly easy to implement. I suppose pythonw.exe wouldn't need the same treatment, as people won't invoke it manually. I guess that option wouldn't be available to non-admin users, though. > My own solution, on systems where I haven't bothered to add \python25 > and python25\Scripts to the PATH, is to simply use > > \python25\python > > With tab expansion enabled by default it's easy enough. Same for me. That's why I like Python being installed in the root directory (also a common complaint - why doesn't it install into the Programs Files folder?) Regards, Martin
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