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?
Gary R.
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.
As developers, we run all of our code from the examples directory
(which has the data and files) but now that the website has actually
become useful, more and more people are running examples downloaded
from the server, and so they don't have the extra code and files that
some examples need. We have mostly resolved this problem in svn HEAD,
but will be a little while before it makes it into a production
release, so you may want to check out the examples from svn
svn co matplotlib download | SourceForge.net
mpl_examples
JDH
demo_image.py (400 Bytes)
On Mon, Aug 10, 2009 at 5:05 AM, Gary Ruben<gruben@...636...> 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?
John Hunter 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?
On Mon, Aug 10, 2009 at 5:05 AM, Gary Ruben<gruben@...636...> wrote:
--
Neil Pilgrim
Thanks John.
John Hunter wrote:
On Mon, Aug 10, 2009 at 5:05 AM, Gary Ruben<gruben@...636...> 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.
<snip>
John,
I changed the axes_grid examples to use get_sample_data and committed
them to the svn yesterday.
However, these examples won't work unless the user uses mpl from the
svn (I don't think get_sample_data is in 0.99 maint).
But, at some point during the last dev cycle, I think the gallery in
our web page started to show the examples from the svn. So, if we're
going to repeat it again (I mean pushing the docs from the svn), I
think I'd better revert those changes I made. And maybe modify them to
run standalone.
Regards,
-JJ
On Mon, Aug 10, 2009 at 7:27 AM, John Hunter<jdh2358@...287...> wrote:
On Mon, Aug 10, 2009 at 5:05 AM, Gary Ruben<gruben@...636...> 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.As developers, we run all of our code from the examples directory
(which has the data and files) but now that the website has actually
become useful, more and more people are running examples downloaded
from the server, and so they don't have the extra code and files that
some examples need. We have mostly resolved this problem in svn HEAD,
but will be a little while before it makes it into a production
release, so you may want to check out the examples from svnsvn co matplotlib download | SourceForge.net
mpl_examplesJDH
------------------------------------------------------------------------------
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
matplotlib-users List Signup and Options
I can keep building the website off the 0.99 branch until release 1.0,
so this shouldn't be a problem.
JDH
On Mon, Aug 10, 2009 at 10:23 AM, Jae-Joon Lee<lee.j.joon@...287...> wrote:
John,
I changed the axes_grid examples to use get_sample_data and committed
them to the svn yesterday.
However, these examples won't work unless the user uses mpl from the
svn (I don't think get_sample_data is in 0.99 maint).
But, at some point during the last dev cycle, I think the gallery in
our web page started to show the examples from the svn. So, if we're
going to repeat it again (I mean pushing the docs from the svn), I
think I'd better revert those changes I made. And maybe modify them to
run standalone.