On 17/10/13 10:59, Antonio Cuni wrote:
Hi,
On 15/10/13 12:45, matti picus wrote:
and what about cloning the numpy repo into bitbucket/pypy to make it
more of a
"pypy owned" thing?
I think it's a good idea.
I propose the following:
1) we move your repo to bitbucket/pypy/numpypy
2) we packa
Hi,
On 15/10/13 12:45, matti picus wrote:
and what about cloning the numpy repo into bitbucket/pypy to make it more of a
"pypy owned" thing?
I think it's a good idea.
I propose the following:
1) we move your repo to bitbucket/pypy/numpypy
2) we package numpypy, so that people can just do "p
and what about cloning the numpy repo into bitbucket/pypy to make it more
of a "pypy owned" thing?
Matti
On Tue, Oct 15, 2013 at 1:18 PM, Romain Guillebert wrote:
> Hi Matti
>
> I think we should remove numpy.py and package the pypy-hack branch
> (even if it's not stable yet) so that people can
Hi Matti
I think we should remove numpy.py and package the pypy-hack branch
(even if it's not stable yet) so that people can use it directly.
Cheers
Romain
On Tue, Oct 15, 2013 at 6:15 AM, Matti Picus wrote:
> I have been working to get numfocus benchmarks written for numpy to run on
> numpypy
On Tue, 2013-10-15 at 07:15 +0300, Matti Picus wrote:
>
> I did ask on IRC before the change, and got two positive votes, but
> feel a need for wider consensus.
Does that mean that now one only can import NumPyPy as follows
import numpypy
instead of
import numpy
? If yes, what is goin
I have been working to get numfocus benchmarks written for numpy to run
on numpypy and pypy https://github.com/numfocus/python-benchmarks
The biggest obstacle is actually the need for matplotlib, which is used
internally to produce pretty comparisons between different benchmarks.
Luckily, Ste
