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 less attractive.
Ben Root On Fri, Mar 6, 2015 at 12:51 PM, Charles R Harris <charlesr.har...@gmail.com > wrote: > > > On Fri, Mar 6, 2015 at 10:34 AM, Sebastian <se...@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. > > Chuck > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listinfo/numpy-discussion > >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
