On Aug 11, 2013 4:37 PM, "Andrew Dalke" wrote:
>
> On Aug 11, 2013, at 10:24 PM, Benjamin Root wrote:
> > The idea would be that within numpy (and we should fix SciPy as well),
we would always import numpy._testing as testing, and not import testing.py
ourselves.
>
> The problem is the existing co
Congratulations!!
I have been waiting for a long time to see a nanmean function inside numpy.
I never looked inside this function, but I'm happy seeing this discussion
on github!
Cheers,
Arnaldo.
---
*Arnaldo D'Amaral Pereira Granja Russo*
Lab. de Estudos dos Oceanos e Clima
Instituto de Oc
On Sun, Aug 11, 2013 at 2:24 PM, Benjamin Root wrote:
>
> On Aug 11, 2013 5:02 AM, "Ralf Gommers" wrote:
> >
> >
> >
> >
> > On Sun, Aug 11, 2013 at 3:35 AM, Benjamin Root wrote:
> >>
> >> Would there be some sort of way to detect that numpy.testing wasn't
> explicitly imported and issue a depr
On Aug 11, 2013, at 10:24 PM, Benjamin Root wrote:
> The idea would be that within numpy (and we should fix SciPy as well), we
> would always import numpy._testing as testing, and not import testing.py
> ourselves.
The problem is the existing code out there which does:
import numpy as np
...
n
On Aug 11, 2013 5:02 AM, "Ralf Gommers" wrote:
>
>
>
>
> On Sun, Aug 11, 2013 at 3:35 AM, Benjamin Root wrote:
>>
>> Would there be some sort of way to detect that numpy.testing wasn't
explicitly imported and issue a deprecation warning? Say, move the code
into numpy._testing, import in into the
On Sun, Aug 11, 2013 at 4:27 AM, Ralf Gommers wrote:
>
>
>
> On Wed, Aug 7, 2013 at 3:52 PM, Till Stensitzki wrote:
>
>> Hi,
>> there already a plan to release 1.8? I would like to play around with
>> gufuncs.
>>
>
> No fixed plan I think, but there aren't a lot of blockers:
> https://github.com/
On Wed, Aug 7, 2013 at 3:52 PM, Till Stensitzki wrote:
> Hi,
> there already a plan to release 1.8? I would like to play around with
> gufuncs.
>
No fixed plan I think, but there aren't a lot of blockers:
https://github.com/numpy/numpy/issues?milestone=1&page=1&state=open. Main
issue is the time
On Sun, Aug 11, 2013 at 3:35 AM, Benjamin Root wrote:
> Would there be some sort of way to detect that numpy.testing wasn't
> explicitly imported and issue a deprecation warning? Say, move the code
> into numpy._testing, import in into the namespace as testing, but then have
> the testing.py file