2009/8/14 Dag Sverre Seljebotn da...@student.matnat.uio.no:
There's been some discussion earlier about how starting to write bigger
parts of the NumPy/SciPy codebase in Cython could potentially lower the
barrier of entry.
Also, it could address the 2.x to 3.0 C-API transition problems. I'm
There's been some discussion earlier about how starting to write bigger
parts of the NumPy/SciPy codebase in Cython could potentially lower the
barrier of entry.
Some topics:
* Move towards PEP3118 as the primary scientific data container
rather than ndarray?
* Cython templates?
* Native
On Fri, Aug 14, 2009 at 8:04 AM, Dag Sverre
Seljebotnda...@student.matnat.uio.no wrote:
There's been some discussion earlier about how starting to write bigger
parts of the NumPy/SciPy codebase in Cython could potentially lower the
barrier of entry.
Some topics:
* Move towards PEP3118 as
+1. The topics (especially native SIMD) sound fantastic so far.
David
On 14-Aug-09, at 9:04 AM, Dag Sverre Seljebotn wrote:
There's been some discussion earlier about how starting to write
bigger
parts of the NumPy/SciPy codebase in Cython could potentially lower
the
barrier of entry.
