> What I meant was that we could include an easy_install.py whose sole > function is to ensure that setuptools is installed and then invoke > the "real" easy_install. Thus, the first time you ran easy_install, > a current version would be downloaded, and thereafter the real one > would be runnable. Despite my (well-known) objections to setuptools as the foundation for the .egg format (and everything that comes with it), I think that would be a desirable and easy thing to do. Including a setuptools bootstrapper into the distribution still leaves the choice of actually using setuptools to the end user. 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