Michael McNeil Forbes wrote:
In article [EMAIL PROTECTED],
Travis Oliphant [EMAIL PROTECTED] wrote:
Hmm I know that the code was changed at some point a few months ago
specifically to this behavior because of some concerns Perry, Chris
(people at STScI) had. Originally, field
En/na Colin J. Williams ha escrit::
I'm afraid I'm still baffled. Are you saying that your proposal is
necessary
to preserve compatibility with Python versions before 2.3? Otherwise, it
appears
to introduce clutter with no clear benefit.
I don't find Numexpr in NumPy, are you referring
What is PyQwt3D?
- it is a set of Python bindings for the QwtPlot3D C++ class library
which extends the Qt framework with widgets for 3D data visualization.
PyQwt3D inherits the snappy feel from QwtPlot3D.
The examples at http://pyqwt.sourceforge.net/pyqwt3d-examples.html
show how easy it
Ivan Vilata i Balaguer wrote:
En/na Colin J. Williams ha escrit::
I'm afraid I'm still baffled. Are you saying that your proposal is
necessary
to preserve compatibility with Python versions before 2.3? Otherwise, it
appears
to introduce clutter with no clear benefit.
I don't find
On Sunday 29 October 2006 02:40, Travis Oliphant wrote:
I've committed some fixes to this particular issue that allows setattr
to be used to set field names.
I just started playing with the new recarray: that works great !
Travis, Thanks a lot !
I recently upgraded to numpy 1.0 from 1.0b5. I noticed that numpy.argmax behavior is very strange on object arrays. See below:
(Pdb) numpy.__version__'1.0'
(Pdb) numpy.argmax(numpy.array([2, 3], dtype=object))0(Pdb) numpy.argmax(numpy.array([2, 3], dtype=int))1
(Pdb) numpy.argmax(numpy.array([2,
Line 71 has: data.view(subtype)
This appears to involve a call to __array_finalize__. Is this an
unconditional call?
If not, what are the conditions?
Why not use __init__ to handle these things, since it is always called
after the __new__?
Colin W.
On 10/29/06, Tom Denniston [EMAIL PROTECTED] wrote:
I recently upgraded to numpy 1.0 from 1.0b5. I noticed that numpy.argmax behavior is very strange on object arrays. See below:
(Pdb) numpy.__version__'1.0'
(Pdb) numpy.argmax(numpy.array([2, 3], dtype=object))0(Pdb) numpy.argmax(numpy.array([2,
On 10/29/06, Tom Denniston [EMAIL PROTECTED] wrote:
Oh. My mistake. I thought I had an array of 2 objects which were ints. I actually had an array of one list of 2 ints. It works properly if I construct the array properly.I think there is actually a bug here:
In [61]: sort(array([3,2],
