On 2015/03/06 1:29 PM, Julian Taylor wrote:
> I think the ship for a warning has long sailed. At this point its
> probably more an annoyance for python3 users and will not prevent many
> more python2 users from saving files that can't be loaded into python3.
The point of a warning is that anything
Hi All,
Time to start thinking about numpy 1.10. At the moment there are 21
blockers and 93 PRs. it would be good if we could prioritize the blockers
and the PRs. It might be a good idea to also look at closing some of the
aging PRs. These days it seems to be normal to have 20 or so PRs in
progres
On 07.03.2015 00:20, Pauli Virtanen wrote:
> 06.03.2015, 22:43, Eric Firing kirjoitti:
>> On 2015/03/06 10:23 AM, Pauli Virtanen wrote:
>>> 06.03.2015, 20:00, Benjamin Root kirjoitti:
A slightly different way to look at this is one of sharing data. If I am
working on a system with 3.4 and
06.03.2015, 22:23, Pauli Virtanen kirjoitti:
> 06.03.2015, 20:00, Benjamin Root kirjoitti:
>> 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
06.03.2015, 22:43, Eric Firing kirjoitti:
> On 2015/03/06 10:23 AM, Pauli Virtanen wrote:
>> 06.03.2015, 20:00, Benjamin Root kirjoitti:
>>> 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
On 2015/03/06 10:23 AM, Pauli Virtanen wrote:
> 06.03.2015, 20:00, Benjamin Root kirjoitti:
>> 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
06.03.2015, 20:00, Benjamin Root kirjoitti:
> 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.
pickle i
On Thu, Mar 5, 2015 at 5:07 PM, Charles R Harris
wrote:
> Do line endings in the scripts matter?
>
I have no idea if powershell cares about line endings, but if you are using
git, then you'll want to make sure that your repo is properly configured to
normalize line endings -- then there should b
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
On Fri, Mar 6, 2015 at 10:34 AM, Sebastian 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.
>
-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
Arnd,
I can see where this is an issue. If you are trying to update your code for
Py3, I still think that it would really help to add a version attribute of
some sort to your new HDF files. You can then write a little check in your
access code that looks for this variable. If it is not present, yo
On Fri, 6 Mar 2015, Pauli Virtanen wrote:
> Arnd Baecker web.de> writes:
> [clip]
>> Still I would have thought that this should be working out-of-the box,
>> i.e. without the pickle.loads trick?
>
> Pickle files should be considered incompatible between Python 2 and Python 3.
>
> Python 3 interp
On Fri, Mar 6, 2015 at 7:59 AM, Charles R Harris
wrote:
> Datetime64 seems to use the highest precision
>
> In [12]: result_type(ones(1, dtype='datetime64[D]'), 'datetime64[us]')
> Out[12]: dtype('
> In [13]: result_type(ones(1, dtype='datetime64[D]'), 'datetime64[Y]')
> Out[13]: dtype('
Ah, ye
Arnd Baecker web.de> writes:
[clip]
> Still I would have thought that this should be working out-of-the box,
> i.e. without the pickle.loads trick?
Pickle files should be considered incompatible between Python 2 and Python 3.
Python 3 interprets all bytes objects saved by Python 2 as str and att
On Fri, Mar 6, 2015 at 7:59 AM, Charles R Harris
wrote:
>
>
> On Thu, Mar 5, 2015 at 10:02 PM, wrote:
>>
>> On Thu, Mar 5, 2015 at 12:33 PM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Thu, Mar 5, 2015 at 10:04 AM, Chris Barker
>> > wrote:
>> >>
>> >> On Thu, Mar 5, 2015 at 8:42 AM, Benjamin R
On Thu, Mar 5, 2015 at 10:02 PM, wrote:
> On Thu, Mar 5, 2015 at 12:33 PM, Charles R Harris
> wrote:
> >
> >
> > On Thu, Mar 5, 2015 at 10:04 AM, Chris Barker
> wrote:
> >>
> >> On Thu, Mar 5, 2015 at 8:42 AM, Benjamin Root wrote:
> >>>
> >>> dare I say... datetime64/timedelta64 support?
> >>
17 matches
Mail list logo
