On 03/01/2012 09:29 AM, Sturla Molden wrote:
On 01.03.2012 17:18, Dag Sverre Seljebotn wrote:
are saying we (somehow) stick with supporting "arr.shape[0]" in
the future, and perhaps even support "print arr.shape"? (+ arr.dim,
arr.strides).
What if you just deprecate ndarray support completely, and just focus on
memory views?
Yes, you will break all Cython code in the world depending on ndarrays.
But you will do that anyway by tempering with the interface. And as
changes to the NumPy C API mandates a change to the interface, I see no
reason to keep it. If you are going to break all code, then just do it
completely. It is worse to stick to syntax bloat. There should not be
multiple ways to do the same (like the zen of Python).
Yeah, I proposed this on another thread as one of the options, but the
support wasn't overwhelming at the time...
About the scipy kcdTree issue, the SciPy process of generating Cython
code manually when the code is written makes the problem slightly smaller...
Dag
_______________________________________________
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
