On 06/24/2010 11:57 AM, Florian Berger wrote: > Hi, > > Eric Firing<efir...@hawaii.edu>: >> >> It was *such* a major change that Value and its ilk were completely >> replaced, not moved aside. > > Thanks, I feared as much. :) > > >> look at what you were trying to do with the code, not at how you >> implemented it via Value. > > Well the thing is that *I* did not try anything, as it is third party > code. :) So I fear I have to figure out why the original author found > Value() so appealing. *sigh* > > >> Unless you were using Value et al for your own purposes [...] > > I think that is what he did. :-/
At least for those applications, you might be able to go back to an earlier mpl version, pull out the c++ code and the wrappers for Value, BinOp, etc., and turn them into an independent extension. That might be worthwhile if you have a *lot* of third-party code that is using those things extensively in ways not tied to mpl. I suspect it would not be very difficult. It's a long time since I looked at that code, though. Eric > > Anyway, thanks for the clarification! > > Best, > Florian > ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
