Hi,
I am pleased to announce the availability of NumPy 1.5.1. This bug-fix
release comes almost 3 months after the 1.5.0 release, it contains no new
features compared to 1.5.0.
Binaries, sources and release notes can be found at
https://sourceforge.net/projects/numpy/files/.
Thank you to everyon
On Sat, Nov 20, 2010 at 4:39 PM, Keith Goodman wrote:
> On Fri, Nov 19, 2010 at 7:42 PM, Keith Goodman
> wrote:
> > I should make a benchmark suite.
>
> >> ny.benchit(verbose=False)
> Nanny performance benchmark
>Nanny 0.0.1dev
>Numpy 1.4.1
>Speed is numpy time divided by nanny time
On Sat, Nov 20, 2010 at 3:54 PM, Wes McKinney wrote:
> Keith (and others),
>
> What would you think about creating a library of mostly Cython-based
> "domain specific functions"? So stuff like rolling statistical
> moments, nan* functions like you have here, and all that-- NumPy-array
> only func
On Sat, Nov 20, 2010 at 6:54 PM, Wes McKinney wrote:
> On Sat, Nov 20, 2010 at 6:39 PM, Keith Goodman wrote:
>> On Fri, Nov 19, 2010 at 7:42 PM, Keith Goodman wrote:
>>> I should make a benchmark suite.
>>
ny.benchit(verbose=False)
>> Nanny performance benchmark
>> Nanny 0.0.1dev
>> N
On Sat, Nov 20, 2010 at 6:39 PM, Keith Goodman wrote:
> On Fri, Nov 19, 2010 at 7:42 PM, Keith Goodman wrote:
>> I should make a benchmark suite.
>
>>> ny.benchit(verbose=False)
> Nanny performance benchmark
> Nanny 0.0.1dev
> Numpy 1.4.1
> Speed is numpy time divided by nanny time
>
On Fri, Nov 19, 2010 at 7:42 PM, Keith Goodman wrote:
> I should make a benchmark suite.
>> ny.benchit(verbose=False)
Nanny performance benchmark
Nanny 0.0.1dev
Numpy 1.4.1
Speed is numpy time divided by nanny time
NaN means all NaNs
Speed TestShapedty
On Sat, Nov 20, 2010 at 2:05 PM, Pauli Virtanen wrote:
> On Sat, 20 Nov 2010 20:57:07 +, Pauli Virtanen wrote:
> [clip]
> > There are more unnecessary merge commits in the git history.
>
> I did a forced push to clear those up.
>
>
It was a pull from upstream to update that did it, when I not
Actually,
I do use spec when I have synchotron experiments. But why are your files so
large?
On Nov 16, 2010 9:20 AM, "Darren Dale" wrote:
> I am wrapping up a small package to parse a particular ascii-encoded
> file format generated by a program we use heavily here at the lab. (In
> the unlikely
On Sat, 20 Nov 2010 20:57:07 +, Pauli Virtanen wrote:
[clip]
> There are more unnecessary merge commits in the git history.
I did a forced push to clear those up.
--
Pauli Virtanen
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http:
Hi,
There are more unnecessary merge commits in the git history.
Before you do "git push", check
git log --oneline --graph
git log --oneline --graph upstream/maintenance/1.5.x..
so that you don't push unnecessary stuff. (Also, don't use "git pull".)
$ git log --oneline
On Sat, 20 Nov 2010 10:01:50 -0500, Darren Dale wrote:
> I just installed numpy for both python2 and 3 from an up-to-date
> checkout of the 1.5.x branch.
>
> I am attempting to cythonize the following code with cython-0.13:
I think you should ask on the Cython list -- I don't think this issue
in
I just installed numpy for both python2 and 3 from an up-to-date
checkout of the 1.5.x branch.
I am attempting to cythonize the following code with cython-0.13:
---
cimport numpy as np
import numpy as np
def test():
cdef np.ndarray[np.float64_t, ndim=1] ret
ret_arr = np.zeros((20,), dtype=
12 matches
Mail list logo
