Hi, Feedback, from Travis Oliphant at EuroPython: libdynd (https://github.com/ContinuumIO/libdynd) might be the longer-term future of NumPy, and it looks like it would be much more natural to bind to it from PyPy (via cffi). Worth a look I believe. It certainly looks to me like such a cffi binding would be much more user-friendly than numpypy, in the sense that missing functionality would be far easier to contribute back. A bientôt, Armin.
Hi, this looks interesting, but from a quick look it seems they are only offering a C++ API? In that case, it might be better/easier to wrap it through cppyy than cffi. Also, did Travis told you what are the plans for scipy? On Fri, Jul 25, 2014 at 10:24 AM, Armin Rigo <arigo@tunes.org> wrote:
Hi,
Feedback, from Travis Oliphant at EuroPython: libdynd (https://github.com/ContinuumIO/libdynd) might be the longer-term future of NumPy, and it looks like it would be much more natural to bind to it from PyPy (via cffi). Worth a look I believe. It certainly looks to me like such a cffi binding would be much more user-friendly than numpypy, in the sense that missing functionality would be far easier to contribute back.
A bientôt,
Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Hi, On 26 July 2014 11:19, Antonio Cuni <anto.cuni@gmail.com> wrote:
this looks interesting, but from a quick look it seems they are only offering a C++ API? In that case, it might be better/easier to wrap it through cppyy than cffi.
One or the other, yes.
Also, did Travis told you what are the plans for scipy?
No. As far as I know the basic library is still in development. It's just that I have somehow a feeling that the current speed at which numpypy progresses is rather slow, and it has a huge existing code base of expectations as well as messy backward-compatibility requirements. If we could instead throw that away and attach our wagon to the newer development, even if it takes another couple of years before it becomes usable, then it seems like a long-term win to me. Also, a cffi or cppyy version seems easier than a RPython version for third-party contributors to help maintain, too. A bientôt, Armin.
Did Travis seem to indicate they would accept contributions from outside toward making a new ndarray implementation a reality? Until we can find a wagon to hitch our minimal efforts to, I will keep working slowly on micronumpy. It seems useful for some tasks, and will be even more so once linalg LAPACK/BLAS is supported (i.e. once we can invert a large matrix). Matti On 31/07/2014 6:29 PM, Armin Rigo wrote:
Hi,
On 26 July 2014 11:19, Antonio Cuni <anto.cuni@gmail.com> wrote:
this looks interesting, but from a quick look it seems they are only offering a C++ API? In that case, it might be better/easier to wrap it through cppyy than cffi. One or the other, yes.
Also, did Travis told you what are the plans for scipy? No. As far as I know the basic library is still in development. It's just that I have somehow a feeling that the current speed at which numpypy progresses is rather slow, and it has a huge existing code base of expectations as well as messy backward-compatibility requirements. If we could instead throw that away and attach our wagon to the newer development, even if it takes another couple of years before it becomes usable, then it seems like a long-term win to me. Also, a cffi or cppyy version seems easier than a RPython version for third-party contributors to help maintain, too.
A bientôt,
Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Hi Matti, On 1 August 2014 07:01, Matti Picus <matti.picus@gmail.com> wrote:
Did Travis seem to indicate they would accept contributions from outside toward making a new ndarray implementation a reality?
I didn't ask (and am not sure why you mean by) a new ndarray implementation. I did ask him about making a cffi interface to the C++ libdynd library that would be usable from both CPython and PyPy, and he was certainly interested and said it was in line with the foreseen usage of libdynd. A bientôt, Armin.
participants (3)
-
Antonio Cuni -
Armin Rigo -
Matti Picus