On Mon, Jul 28, 2008 at 13:56, John Hunter
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 state is persisting between python sessions. This appears to be platform specific, because I have only been able to verify it on 1 platform (quad code xeon 64 bit running fedora) but not on another (solaris x86).
Can you make a new, smaller self-contained example? I suspect stale .pyc files. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco