The ufunc approach makes sense.
Something like abs2 is essential for anyone who does signal processing
simulations using NumPy.
Phillip
On Sat, Oct 10, 2015 at 11:29 AM, Nathaniel Smith wrote:
> On Oct 10, 2015 10:50 AM, "Charles R Harris"
> wrote:
On Fri, Oct 9, 2015 at 10:32 PM, Phillip Feldman <
phillip.m.feld...@gmail.com> wrote:
> Hello Nathaniel,
>
> It is hard to say what is normative practice with NumPy, because there are
> at least three paradigms:
>
> (1) Some operations are implemented as methods of the `ndarray` class.
> `sum`
On Oct 10, 2015 10:50 AM, "Charles R Harris"
wrote:
>
> On Sat, Oct 10, 2015 at 11:14 AM, Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
>>
>> > We tend to avoid adding methods. 2) would be a very easy enhancement,
just a slight modification of sqr.
>>
>> Did
On Sat, Oct 10, 2015 at 11:14 AM, Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> > We tend to avoid adding methods. 2) would be a very easy enhancement,
> just a slight modification of sqr.
>
> Did you mean `np.square`? Sadly, that doesn't do the right thing:
> `np.square(1+1j)` yields
Hi,
I see that there are no docs for 1.10 on docs.scipy.org yet, and the
development version docs are from Nov'14. Anyone with permissions want to
look at rectifying that situation?
Also, building development version docs on TravisCI after each merge would
be useful (for Numpy and Scipy). A
Bokeh also uses TravisCI, and we automatically build deploy docs on "dev"
builds and releases, using encrypted Travis variables to store the necessary
credentials. In case any of that sounds useful, most of the machinery is in
these files: