Well, after the changes today the only setuptools modification to the setup.py file is the addition of the "namespace_packages =3D ['matplotlib.toolkits']" for basemap support and eggs. So I think the `python setup_bdist_egg.py` is a good idea. I'll add it barring any objections (which I doubt there will be). - Charlie On 1/26/06, Fernando Perez <Fer...@co...> wrote: > Andrew Straw wrote: > > I'm myself not 100% sure we want to use this patch, but I think perhaps > > it's better -- people who happen to have setuptools installed don't get > > setuptools-built packages unless they ask for them. > > which is a big plus: recently I couldn't get matplotlib to install with a > plain 'setup.py install' because setuptools was found in my path, but bro= ken > (as it seems to be most of the time for me: I hate setuptools with a pass= ion, > for reasons too long to get into right now). > > Making sure that the mere _presence_ of setuptools in your path doesn't a= ll of > a sudden break all manner of things for matplotlib is a big plus. > > You could always ship a little script specifically to build the egg, alon= g the > lines of > > http://projects.scipy.org/ipython/ipython/browser/ipython/trunk/setup_bdi= st_egg.py > > Normal builds would be uncontaminated by setuptools, and those who happen= to > like it can just call > > python setup_bdist_egg.py > > instead of > > python setup.py bdist_egg > > > In the interest of robustness for matplotlib, I think that sandboxing > setuptools a little more is a good idea. > > Cheers, > > f >