On Mon, 21 Feb 2011 16:03:43 -0500, Skipper Seabold wrote:
[clip]
> I had to reinstall scipy, matplotlib, etc. when I changed from 1.6.0
> back to 1.5.1.
Yes, it should be backward compatible (you should be able use binaries
compiled with 1.5.1 on 1.6.0), but not forward compatible (binaries
com
On Mon, Feb 21, 2011 at 3:49 PM, Pauli Virtanen wrote:
> On Mon, 21 Feb 2011 15:09:05 -0500, Skipper Seabold wrote:
> [clip]
>> Should I file a ticket?
>
> Yes.
http://projects.scipy.org/numpy/ticket/1748
>
> [clip]
>> PS. Is there an incompatibility of numpy 1.5.1 and numpy 1.6.0 trunk for
>> p
On Mon, 21 Feb 2011 15:09:05 -0500, Skipper Seabold wrote:
[clip]
> Should I file a ticket?
Yes.
[clip]
> PS. Is there an incompatibility of numpy 1.5.1 and numpy 1.6.0 trunk for
> packages that depend on numpy?
It should be binary compatible.
--
Pauli Virtanen
___
I get a lot of errors and failures running our tests with most recent
numpy trunk. One in particular (so far) seems to be a bug.
In [1]: import numpy as np
In [2]: np.__version__
Out[2]: '1.6.0.dev-c50af53'
In [3]: tmp_arr = np.array([['black'],['white'],['other']])
In [4]: tmp_arr.astype('str'
Hi,
Just wanted to respond to
http://comments.gmane.org/gmane.comp.python.numeric.general/42084
*CORTESI: I have installed ActiveState's Python 3 packages on Mac OS X
10.6.6. [...] What can I do to persuade numpy to install? Must I build it
from sourceto get it to use Python 3?
RALF: [...] there
===
Announcing ViTables 2.1
===
After a long period retired from development activities I'm happy to come back
and present ViTables 2.1, the latest release of this viewer for PyTables/HDF5
files.
As it happens with the entire PyTables family, the main stren
