On Tue, Aug 4, 2009 at 5:11 PM, Tarek Ziadé<ziade.ta...@gmail.com> wrote: > On Tue, Aug 4, 2009 at 11:01 PM, Jim Fulton<j...@zope.com> wrote: >> I'll be surprised if all that's needed to make buildout work with >> Distribute is a new bootstrap script. > > well, after the bootstrap is over you end up with : > > - a setuptools distribution still installed *but* empty > - a distribute distribution installed that provides the setuptools > package, the pkg_resources.py, site.py and easy_install.py files > > which means that any code running afterwards will think setuptools is > installed and will import distrbute's files > > at the moment I can see one case where it won't work: an __import__ > done on the setuptools location > but so far my Plone works (this is the most complex use case I have so far)
Buildout will often reinstall setuptools, depending which version it thinks it needs. I'd expect this to defeat whatever you've done. >> Note that my long term plan is to remove setuptools (or distribute) as >> a dependency of buildout, although I don't know when I'll have time to >> get to that. > > until then I don't have a better plan to allow users to switch to the > fork, unless zc.buildout > is changed so setuptools installation it's not harcoded anymore in there I guess I don't see an urgent need for buildout to use distribute. If distribute is truly a setuptools clone, I suppose that the project name to use could be configurable in buildout. This would take some work, but probably not that much. That seems cleaner and less brittle than hacking installed setuptools distributions. Jim -- Jim Fulton _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
