Eric Smith wrote: > Or for that matter a plain "pysetup". It would > be the one that a plain "python" would get you. If 'pysetup' is simply a shell script that invokes 'python -m setup' using the current search path, I guess that's true. On Windows, however, it seems to me that the current 'python setup.py' scheme has advantages, since it lets you simply invoke 'setup.py' and rely on file associations to get you the current python. Supporting either 'python -m setup' or 'pysetup' out of the box would require install-time path hacking of the sort that some people are uncomfortable about. -- Greg
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