I am not very familiar with the NumPy development and release
strategy, but is there any chance this fix could be included in 1.7.0?
https://github.com/numpy/numpy/pull/2798
This is the source of a recently reported bug in h5py and there is
nothing I can do to work around it without breaking othe
While we are at it, back-porting
https://github.com/numpy/numpy/pull/2730
Would give a good speed up for an LTS.
I made a new PR that do this back-port:
https://github.com/numpy/numpy/pull/2847
Fred
On Mon, Dec 17, 2012 at 11:46 AM, David Warde-Farley
wrote:
> A bit off-topic, but could so
A bit off-topic, but could someone have a look at
https://github.com/numpy/numpy/pull/2699 and provide some feedback?
If 1.7 is meant to be an LTS release, this would be a nice wart to
have out of the way. The Travis failure was a spurious one that has
since been fixed.
On Sat, Dec 15, 2012 at 6:
Hi,
I added a new issue that is a regression about numpy.ndindex() that we
already talked. But it was a duplicate[1], so I closed it. I think it
got lost as the ticket wasn't marked for 1.7 milestone. Ccan someone
do it? I don't have the right.
This regression break something in Theano. We could
On Mon, Dec 17, 2012 at 12:26 AM, Nathaniel Smith wrote:
> On 16 Dec 2012 23:01, "Charles R Harris"
> wrote:
> >
> >
> >
> > On Sun, Dec 16, 2012 at 3:50 PM, Ondřej Čertík
> wrote:
> >>
> >> Thanks Ralf and Nathan,
> >>
> >> I have put high priority on the issues that need to be fixed before th
On 16 Dec 2012 23:01, "Charles R Harris" wrote:
>
>
>
> On Sun, Dec 16, 2012 at 3:50 PM, Ondřej Čertík
wrote:
>>
>> Thanks Ralf and Nathan,
>>
>> I have put high priority on the issues that need to be fixed before the
rc1.
>> There are now 4 issues:
>>
>>
https://github.com/numpy/numpy/issues?lab
On Sun, Dec 16, 2012 at 3:50 PM, Ondřej Čertík wrote:
> Thanks Ralf and Nathan,
>
> I have put high priority on the issues that need to be fixed before the
> rc1.
> There are now 4 issues:
>
>
> https://github.com/numpy/numpy/issues?labels=priority%3A+high&milestone=3&page=1&state=open
>
> I am wo
Thanks Ralf and Nathan,
I have put high priority on the issues that need to be fixed before the rc1.
There are now 4 issues:
https://github.com/numpy/numpy/issues?labels=priority%3A+high&milestone=3&page=1&state=open
I am working on the mingw one, as that one is the most difficult.
Ralf (or anyo
On Sun, Dec 16, 2012 at 3:17 AM, Nathaniel Smith wrote:
> #294 is a regression, so probably should be considered release critical. I
> can't tell if #2750 is a real problem or not. #378 looks serious, but
> afaict has actually been fixed even though the bug is still marked open? At
> least fixed
#294 is a regression, so probably should be considered release critical. I
can't tell if #2750 is a real problem or not. #378 looks serious, but
afaict has actually been fixed even though the bug is still marked open? At
least fixed in 1.7.x?
On 15 Dec 2012 23:52, "Ondřej Čertík" wrote:
> Hi,
>
>
Hi,
If you go to the issues for 1.7 and click "high priority":
https://github.com/numpy/numpy/issues?labels=priority%3A+high&milestone=3&state=open
you will see 3 issues as of right now. Two of those have PR attached.
It's been a lot of work
to get to this point and I'd like to thank all of you
11 matches
Mail list logo
