Michael Droettboom wrote:
John Hunter wrote:
In unrelated news, I am not in favor of the recent change to warn on
non-GUI backends when show is called. I realize this may sometimes
cause head-scratching behavior for some users who call show and no
figure pops up, but I think this must be
On Thu, Oct 9, 2008 at 6:14 AM, Michael Droettboom [EMAIL PROTECTED] wrote:
If 2) in the choices above is the case you are concerned about, and
you want this warning feature in this case, we can add an rc param
which is autoset at build time, something like show.warn =
True|False since the
John Hunter wrote:
On Wed, Oct 8, 2008 at 8:40 PM, Eric Firing [EMAIL PROTECTED] wrote:
Thanks for doing this--it has already helped me in my testing of the
gappy-path simplification support, which I have now committed. As you
suggested earlier, I included in path.py a check for a
The patch in that last message of mine was clearly not quite right. I
have gone through several iterations, and have seemed tantalizingly
close, but I still don't have it right yet. I need to leave it alone
for a while, but I do think it is important to get this working
correctly
Eric Firing wrote:
Michael Droettboom wrote:
Eric Firing wrote:
Mike, John,
Because path simplification does not work with anything but a
continuous line, it is turned off if there are any nans in the
path. The result is that if one does this:
import numpy as np
xx = np.arange(20)
Michael Droettboom wrote:
Eric Firing wrote:
Michael Droettboom wrote:
Eric Firing wrote:
Mike, John,
Because path simplification does not work with anything but a
continuous line, it is turned off if there are any nans in the
path. The result is that if one does this:
On Wed, Oct 8, 2008 at 11:37 AM, Michael Droettboom [EMAIL PROTECTED] wrote:
I figured this out. When this happens, a RuntimeError(Agg rendering
complexity exceeded) is thrown.
Do you think it is a good idea to put a little helper note in the
exception along the lines of
throw Agg
John Hunter wrote:
On Wed, Oct 8, 2008 at 11:37 AM, Michael Droettboom [EMAIL PROTECTED] wrote:
I figured this out. When this happens, a RuntimeError(Agg rendering
complexity exceeded) is thrown.
Do you think it is a good idea to put a little helper note in the
exception along
Michael Droettboom wrote:
John Hunter wrote:
On Wed, Oct 8, 2008 at 11:37 AM, Michael Droettboom [EMAIL PROTECTED]
wrote:
I figured this out. When this happens, a RuntimeError(Agg rendering
complexity exceeded) is thrown.
Do you think it is a good idea to put a little helper
On Wed, Oct 8, 2008 at 8:40 PM, Eric Firing [EMAIL PROTECTED] wrote:
Thanks for doing this--it has already helped me in my testing of the
gappy-path simplification support, which I have now committed. As you
suggested earlier, I included in path.py a check for a compatible codes
array.
The
Eric Firing wrote:
Mike, John,
Because path simplification does not work with anything but a
continuous line, it is turned off if there are any nans in the path.
The result is that if one does this:
import numpy as np
xx = np.arange(20)
yy = np.random.rand(20)
#plot(xx, yy)
Michael Droettboom wrote:
Eric Firing wrote:
Mike, John,
Because path simplification does not work with anything but a
continuous line, it is turned off if there are any nans in the path.
The result is that if one does this:
import numpy as np
xx = np.arange(20)
yy =
Mike, John,
Because path simplification does not work with anything but a continuous
line, it is turned off if there are any nans in the path. The result is
that if one does this:
import numpy as np
xx = np.arange(20)
yy = np.random.rand(20)
#plot(xx, yy)
yy[1000] = np.nan
plot(xx,
13 matches
Mail list logo
