Ah, great, glad to hear that. Thx!
On Wed, Sep 23, 2015 at 5:43 PM, Matthew Brett
wrote:
> Hi,
>
> On Wed, Sep 23, 2015 at 5:30 PM, Fernando Perez
> wrote:
> > Chance this will be merged into 1.10? I know there's an rc floating out
> > there for 1.10, and this sounds like an actual bug... Woul
Hi,
On Wed, Sep 23, 2015 at 5:30 PM, Fernando Perez wrote:
> Chance this will be merged into 1.10? I know there's an rc floating out
> there for 1.10, and this sounds like an actual bug... Would be great to
> have a solid 1.10 for the 3.5 crowd :)
1.10 already contains the f2py fixes, luckily..
Chance this will be merged into 1.10? I know there's an rc floating out
there for 1.10, and this sounds like an actual bug... Would be great to
have a solid 1.10 for the 3.5 crowd :)
On Wed, Sep 23, 2015 at 5:24 PM, Matthew Brett
wrote:
> Hi,
>
> I'm afraid our very helpful testers have found a
Hi,
I'm afraid our very helpful testers have found a problem with f2py and
Numpy 1.9.3 (and earlier):
https://github.com/numpy/numpy/issues/6348
I think we need a numpy 1.9.4 soon therefore.
I started a branch / PR here : https://github.com/numpy/numpy/pull/6350
Any other fixes? Carl - do yo
