Mon, 28 Jul 2008 13:56:52 -0500, John Hunter wrote:
> In trying to track down a bug in matplotlib, I have come across tsome
> very strange numpy behavior. Basically, whether or not I call
> np.seterr('raise') or not in a matplotlib demo affects the behavior of
> seterr in another (pure numpy) scr
On Mon, Jul 28, 2008 at 2:35 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> Both, if the behavior exhibits itself without the npy file. If it only
> exhibits itself with an npy involved, then we have some more
> information about where the problem might be.
OK, I'll see what I can come up with. In
On Mon, Jul 28, 2008 at 14:30, John Hunter <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 28, 2008 at 2:02 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
>> On Mon, Jul 28, 2008 at 13:56, John Hunter <[EMAIL PROTECTED]> wrote:
>>> In trying to track down a bug in matplotlib, I have come across tsome
>>> very
On Mon, Jul 28, 2008 at 2:02 PM, Robert Kern <[EMAIL PROTECTED]> wrote:
> On Mon, Jul 28, 2008 at 13:56, John Hunter <[EMAIL PROTECTED]> wrote:
>> In trying to track down a bug in matplotlib, I have come across tsome
>> very strange numpy behavior. Basically, whether or not I call
>> np.seterr('ra
On Mon, Jul 28, 2008 at 13:56, John Hunter <[EMAIL PROTECTED]> wrote:
> In trying to track down a bug in matplotlib, I have come across tsome
> very strange numpy behavior. Basically, whether or not I call
> np.seterr('raise') or not in a matplotlib demo affects the behavior of
> seterr in another
In trying to track down a bug in matplotlib, I have come across tsome
very strange numpy behavior. Basically, whether or not I call
np.seterr('raise') or not in a matplotlib demo affects the behavior of
seterr in another (pure numpy) script, run in a separate process.
Something about the numpy sta
