John Hunter wrote: > On Mon, Aug 10, 2009 at 5:05 AM, Gary Ruben<gru...@bigpond.net.au> wrote: >> Many of the axes_grid examples in the thumbnail gallery don't work out >> of the box with the latest matplotlib 0.99 because they rely on >> demo_image and demo_axes_divider modules. Should these have been >> packaged with 0.99 or were they left out deliberately? > > We've addressed this already in svn HEAD, but the fixes won't be out > until mpl1.0. For now, just drop the attached file in the same > directory as your example code (you may also need to touch a > __init__.py in that dir. [...]
What about some kind of 'requires(version)'? (assert? module function?) Maybe even with a latest version that it supported for code that is out of date? Then if an example (essentially a test?) is added in tandem with some new code, then the 'requires(version)' code can be updated. Similar checks could be made if examples are updated to support larger-scale changes (which are hopefully not as common!). This could also allow examples to be tagged with the required version, and even sorted according to 'added in this version'. I run debian lenny with its version of mpl, and I was very glad when I upgraded to it, in order not to have to regularly compile mpl if there was some new feature. However, if I could clearly see from examples/thumbnails which features required which version, then this would make things a little clearer, and balance a need to upgrade perhaps? Thoughts? -- Neil Pilgrim ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
