Re: [matplotlib-devel] How to exclude some examples to be built for doc?

2010-07-19 Thread John Hunter
On Mon, Jul 19, 2010 at 5:22 PM, Eric Firing wrote: > It would be OK to retain some examples with live downloading, but they > should not be required for doc generation or for basic testing of mpl. > They don't contribute anything essential to either. The primary motivation for the get_sample_dat

Re: [matplotlib-devel] refactoring of show

2010-07-19 Thread Fernando Perez
Hey guys, On Mon, Jul 19, 2010 at 4:07 PM, Eric Firing wrote: > > Please leave out the -a.  It is harmful, not helpful, for mpl.  This may > mean we need to change mpl and/or ipython, or the documentation, to > prevent problems with the -a option; but I think you will find that if > you leave out

Re: [matplotlib-devel] refactoring of show

2010-07-19 Thread Eric Firing
On 07/19/2010 10:34 AM, Erik Tollerud wrote: > I've been keeping more or less up on the .11 development ipython, > under Ubuntu 9.10 (10.4 when I get around to it...). For each of the > backends I do the following in an interactive session that starts with > no profile or -pylab or anything:: > >

Re: [matplotlib-devel] refactoring of show

2010-07-19 Thread Eric Firing
On 07/19/2010 10:34 AM, Erik Tollerud wrote: > I've been keeping more or less up on the .11 development ipython, > under Ubuntu 9.10 (10.4 when I get around to it...). For each of the > backends I do the following in an interactive session that starts with > no profile or -pylab or anything:: > >

Re: [matplotlib-devel] How to exclude some examples to be built for doc?

2010-07-19 Thread Eric Firing
On 07/19/2010 11:10 AM, Sandro Tosi wrote: > Hello, > you know this question might seems strange, but I'd like to avoid some > examples to be built when creating documentation. > > Those examples are the one using mpl.cbook.get_sample_data() to > retrieve data files from the remote svn. In Debian w

[matplotlib-devel] How to exclude some examples to be built for doc?

2010-07-19 Thread Sandro Tosi
Hello, you know this question might seems strange, but I'd like to avoid some examples to be built when creating documentation. Those examples are the one using mpl.cbook.get_sample_data() to retrieve data files from the remote svn. In Debian we are not allowed to prepare a package that downloads

Re: [matplotlib-devel] refactoring of show

2010-07-19 Thread Erik Tollerud
I've been keeping more or less up on the .11 development ipython, under Ubuntu 9.10 (10.4 when I get around to it...). For each of the backends I do the following in an interactive session that starts with no profile or -pylab or anything:: import matplotlib matplotlib.interactive(True) matplotli

Re: [matplotlib-devel] rendering problem in mplot3d

2010-07-19 Thread Ryan May
On Sun, Jul 18, 2010 at 6:16 PM, Benjamin Root wrote: > A few corrections.  First, I wrong, it is unusual.  The second axes that I > noticed in a 2d case came from a colorbar being added.  Second, in the 3d > case, it was the Axes3DSubplot object being added twice, not the regular > object like I

Re: [matplotlib-devel] HTML5 Matplotlib Backend

2010-07-19 Thread Nathaniel Smith
On Fri, Jul 16, 2010 at 10:21 AM, Ryan Wagner wrote: > (Michael Droettboom) > >>> The display at the bottom that says "Cursor at: X, Y" is in pixels, not >>> in > >>> data units. ?It would be great if this could display data units, though > >>> being general enough to support custom scales (eg. lo

[matplotlib-devel] HTML5 Matplotlib Backend

2010-07-19 Thread Ryan Wagner
(Michael Droettboom) >> The display at the bottom that says "Cursor at: X, Y" is in pixels, not in >> data units. ?It would be great if this could display data units, though >> being general enough to support custom scales (eg. log) and projections (eg. >> polar) may be tricky without making a

[matplotlib-devel] Patchs for changing ticks messing up mplot3d and tick-get/setters

2010-07-19 Thread Erik Tollerud
I noticed some odd behavior when trying to set ticks on 3d plots made using mplot3d.Axes3D ... specifically, if you tries to access any of the 3D axes and change the ticks, it would result in a plot all squashed to one side (indicating some sort of projection problem). After a bit of digging, I dis