On Thursday 05 April 2007 06:44:36 am Edin Salkovic wrote: > On 4/5/07, Darren Dale <[EMAIL PROTECTED]> wrote: > > I considered this when setuptools became a requirement for python-2.3 > > installs, but decided against it. My reasoning was that the unfamiliar > > user would go to install matplotlib, and see setup.py and ez_setup and > > get confused. Maybe it should go in a subdirectory in our tree? > > Just to clear things up, in case there's some misunderstanding: > ez_setup would be a dir in both cases. You are suggesting that the > ez_setup dir should be put somewhere other than in the current > matplotlib toplevel dir (where 'setup.py' resides). Am I correct?
Sorry, there is some confusion, probably on my part. I was thinking of the ez_setup.py file, which suggests that you can run it to install it, or drop it in your distribution next to setup.py, either way would be sufficient. I though it would be a bad idea to have a setup.py and an ez_setup.py in the same directory. We would get people running ez_setup.py and then writing the lists asking why they cant import pylab. Darren ------------------------------------------------------------------------- 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
