Dave Peterson wrote: > That said, given the upcoming release of Traits 3 this situation may get > a little crazier. T2 and T3 are not fully api compatible, though they > are very close. So I suspect version numbers are going to play a > larger role in the future. Is there anything we can do in the T3 > release to make resolution of this upcoming issue easier to deal with > for the matplotlib team? One point probably worth mentioning is that, > IIRC, we currently rely on T3 being installed with egg meta-data in > order to determine an accurate version number.
Whether, or to what extent, mpl starts depending on traits is still open; but if we do depend on it, I think we should simply require T3 as an external dependency. If that requires some slight modifications of Darren's code, which was written for T2, I expect the changes will be easy. Three questions: 1) To what extent would the range of T3 eggs cover the various platforms on which people run mpl? 2) For uncovered cases, should T3 be easy to build and install? 3) My recollection is that setuptools was determined to be causing a hit to the startup time, and mpl is already sluggish in starting up. Is there any more insight or progress on this front? Is there a way to use traits in mpl without increasing the startup time? I gather from the lists that we are still not out of the woods with respect to making mpl (and scipy, even more) easy to install, and ideally easy to build from svn, for nearly all users; I would not want to see us start depending on traits if this will make the present bad situation worse. Thanks. Eric ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
