[Cython] CEP 513 - Unified Python and Cython namespaces

Robert Bradshaw robertwb at math.washington.edu
Sat Apr 12 19:12:38 CEST 2008


On Apr 12, 2008, at 6:42 AM, Dag Sverre Seljebotn wrote:

> Robert Bradshaw wrote:
>> I added several comments. I'm not convinced it will make things  
>> clearer (or if it will muddy things up even more) but definitely  
>> food for thought.
> Thanks, your comments definitely helped me seperate and present the  
> concepts better. I renamed the page and moved some stuff around; it  
> can now be found here:
>
> http://wiki.cython.org/enhancements/overlaypythonmodules
> http://wiki.cython.org/enhancements/builtins
>
> Clarity: It might be a matter of taste. The latter link is about  
> something I think it makes the Cython language "less heavy" by  
> removing a few special cases that's not allowed today. The idea in  
> the former link I think will be a little complicated but as clear  
> as the alternative I see; which is magical rewrites in the Cython  
> compiler core and having to use seperate names for the type  
> "c_numpy.ndarray" and the constructor "numpy.ndarray". (Using  
> c_numpy is clearer from a low-level perspective but I think it adds  
> a significant learning curve.)

Just to clarify where you're coming from, where in Cython (as it is  
now) would one every have to use c_numpy.ndarray (rather than using  
numpy.ndarray everywhere)?

> Most of this is not that important now though (though some of it is  
> NumPy-relevant). Nailing a good type argument syntax is more  
> important and can be considered seperately from a usability  
> perspective -- the very first response I got from the NumPy  
> community on the specs was that "the ndarray constructor should  
> take the same parameters as we are used to", when what they were  
> looking at was really a parametrization of the ndarray type.
>
> Dag Sverre



More information about the Cython-dev mailing list