> > This comes up for discussion on a fairly regular basis. I tend towards the > more warnings side myself, but you aren't going to get the current behavior > changed unless you can convince a large bunch of people that it is the right > thing to do, which won't be easy. For one thing, a lot of current code in the > wild would begin to raise warnings that weren't there before. That could also be a good thing for locating bugs, right?
> Or: give me a hint how and where to change the numpy code, and I could try to > write a patch. > > > You have to go down to the C level to deal with this. I guess code containing such warnings must exist in other parts of the numpy library? Paul. _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
