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? If so, I don't see why would anyone be confused by having an ez_setup dir at the top level, but that's just my opinion. In fact, I think that some of the current dirs at toplevel are more confusing ;). Anyway, either way (toplevel or subdir) is fine for me. ez_setup dir will be there only to aid a person that's *building from source* (normaly a dev building from SVN), so he can allways have the latest setuptools installed on *his* system. A person (regular user) that doesn't have setuptools installed, and just wants to do a "easy_install matplotlib" will still have to download the ez_setup.py script from http://peak.telecommunity.com/dist/ez_setup.py , and run it, before installing matplotlib. Then, he'll soon get into the problem of not having the appropriate backend installed, but that's another problem :) Cheers, Edin ------------------------------------------------------------------------- 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
