Robert Bradshaw wrote: > On Feb 2, 2010, at 2:01 PM, Christopher Barker wrote: > > >> Dag Sverre Seljebotn wrote: >> >>> The alternative then appears to be >>> >>> from cython.c.math cimport sqrt >>> from cython.python cimport Py_INCREF >>> >>> but that's awfully verbose. >>> >> I LIKE verbose imports -- that's what "from" is for. The import can be >> verbose (and clear, and unlikely to name clash), while the rest of >> your >> code is as terse as you like. >> >> If this is all cython stuff, it should live in the cython namespace. >> > > > I like clib or libc (with or without the cython prefix) better than > just plain c. There's also the consideration question of supporting > pure mode, currently cython.* is all directives/other builtins, this > conflates the idea a bit. In the C++ branch we now have > cython.operator (where dereference, preincrement, etc. all live). > I'm rather against the cython prefix...I don't feel it is logical that "library stuff" that isn't really implemented in Cython itself lives there. It is a place for "Cython builtins" to me.
There's no difference in principle between, say, stdlib.h and opengl.h. How about just "libc" and "libcpp" then? Dag Sverre > Eventually, for math, it would be nice if Cython called the > corresponding C operators directly when acting on C types. (Dag has > brought this up before.) One caveat is that often Python floats have > better error handling/corner case handling than clib, and also > many .pxds we would like to ship are not necessarily basic Python > modules. > Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
