John Hunter wrote: > On 4/5/07, Edin Salkovic <[EMAIL PROTECTED]> wrote: > >> This would make installing setuptools even easier, since the newest >> ez_setup/seuptools would be downloaded by the user/developer every >> time a "svn update;python setup.py install" is issued. >> >> Are the above changes OK? > > I'm not sure I see the benefit here -- what does it buy us to insure > that we always have the latest ez_setup in our tree?
The purpose of ez_setup.py was to give people a migration path such that they could write project that used setuptools, but ensure that their users wouldn't have to go install another package themselves. It's deprecated now. Don't use it. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
