On Nov 7, 2007, at 7:25 AM, John Hunter wrote: > Is there a reason not to treat > traits like we do dateutil and pytz: check at runtime if it is > installed and if not install it as enthought.traits using Gael's > tarball?
I don't see the check-then-tarball as a feature, but as a significant complication that I have to be aware of when I'm building MatPlotLib. I embed MatPlotLib inside a Macintosh application, so there is a significant amount of packaging and verification that I need to do to ensure a seamless installation for an end-user. I need to know more about Python culture and Python packages, I suppose, but for the moment I'm trying to keep things as straightforward as possible. So for what it's worth, my vote is for limited cleverness in the attempt to resolve dependencies. Let the compile fail. Tell them they need a "real" enthought traits package. Then they can use their package management to make it right. ------------------------------------------------------------------------- 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
