On Nov 7, 2007 12:01 PM, Boyd Waters <[EMAIL PROTECTED]> wrote: > Tell them they need a "real" enthought traits package. Then they can > use their package management to make it right.
This is of course assuming their package management has enthought.traits, which by and large, it won't. I am sympathetic to this view, but our recent experience has been that getting enthought.traits to install properly even for matplotlib developers took a fair amount of work and consultation with the enthought dev team. My concern is that 50% of new and existing users would simply not install or upgrade under these circumstances. The difficultly getting scipy installed followed it for years (that is why mpl never depended on it), and we is in danger of obtaining a similar "difficult to install so I won't upgrade" reputation. I would rather inconvenience a sophisticated developer like you (embedding mpl in an app, following the dev list) primarily because you can take it and work with it. For a newbie, having the install fail and being pointed to a setuptools process they don't understand that may also fail may be the difference between their using matplotlib and not. If you could set a simple flag or environment variable to turn off all the optional install "smarts" that should be enough, no? ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
