FWIW -- updated plots with contribution from Julian Taylor
http://www.onerussian.com/tmp/numpy-vbench-20130701/vb_vb_indexing.html#mmap-slicing
;-)
On Mon, 01 Jul 2013, Yaroslav Halchenko wrote:
> Hi Guys,
> not quite the recommendations you expressed, but here is my ugly
> attempt t
Hi Guys,
not quite the recommendations you expressed, but here is my ugly
attempt to improve benchmarks coverage:
http://www.onerussian.com/tmp/numpy-vbench-20130701/index.html
initially I also ran those ufunc benchmarks per each dtype separately,
but then resulting webpage is loong which
On Mon, 2013-07-01 at 17:54 +0200, Sebastian Berg wrote:
> On Mon, 2013-07-01 at 14:11 +0200, Félix Hartmann wrote:
> > Hi all,
> >
> > I recently upgraded from Numpy 1.6.2 to 1.7.1 on my Debian testing, and
> > then got a bug in a program that was previously working. It turned out
> > that the pr
On Mon, 2013-07-01 at 14:11 +0200, Félix Hartmann wrote:
> Hi all,
>
> I recently upgraded from Numpy 1.6.2 to 1.7.1 on my Debian testing, and
> then got a bug in a program that was previously working. It turned out
> that the problem comes from the np.insert function when the argument
> `axis=-1`
Hi all,
I recently upgraded from Numpy 1.6.2 to 1.7.1 on my Debian testing, and
then got a bug in a program that was previously working. It turned out
that the problem comes from the np.insert function when the argument
`axis=-1` is given.
Here is a minimal example:
>>> u = np.zeros((2,3,4))
>>>
