[Numpy-discussion] numpy pickling problem - python 2 vs. python 3
ben.root at ou.edu
Fri Mar 6 13:00:05 EST 2015
A slightly different way to look at this is one of sharing data. If I am
working on a system with 3.4 and I want to share data with others who may
be using a mix of 2.7 and 3.3 systems, this problem makes npz format much
On Fri, Mar 6, 2015 at 12:51 PM, Charles R Harris <charlesr.harris at gmail.com
> On Fri, Mar 6, 2015 at 10:34 AM, Sebastian <sebix at sebix.at> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>> Hi all,
>> As this also affects .npy files, which uses pickle internally, why can't
>> this be done by Numpy itself? This breaks backwards compatibility in a
>> very bad way in my opinion.
>> The company I worked for uses Numpy and consorts a lot and also has many
>> data in .npy and pickle files. They currently work with 2.7, but I also
>> tried to develop my programs to be compatible with Py 3. But this was
>> not possible when it came to the point of dumping and loading npy files.
>> I think this will be major reason why people won't take the step forward
>> to Py3 and Numpy is not considered to be compatible to Python 3.
> Are you suggesting adding a flag to the files to mark the python version
> in which they were created? The *.npy format is versioned, so something
> could probably be done with that.
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion