At 10:06 PM 6/26/2007 -0700, primco wrote:
On a related note, and to finish of the dismantling of setuptools package management, how do I give the setuptools package itself this treatment?
Some of the things I'd like to do: not use any .pth files for any packages not change site.py or sys.path (PYTHONPATH is ok) at runtime Avoid the included site.py that is generated by installing setuptools itself as single version externally managed. It has a "__boot()" function that does some path management.
What I've done is "setup.py install --root..." setuptools from the source. This made a site.py for me which I just left out of site-packages and it all seems to work. I was able to run Pylons (a pretty good setuptools workout I think) with all dependencies installed in the same unmanaged manner. Did I just get lucky or should I assume that I've safely disabled the package management features of setuptools while still keeping some dynamic things like entrypoints and find_packages working?
Sounds correct to me. The site.py in site-packages wouldn't harm anything, btw, as it would never get imported. I suspect removing it breaks any attempt to use easy_install to install eggs to $PYTHONPATH (probably with a traceback and no sane error message) but perhaps that's what you intend.