On 9 Apr 2013 13:05, "mark florisson" <markflorisso...@gmail.com> wrote: > However, the memoryview class is duplicated in every cython module, which means a memoryview object from another module will fail this check. This is a general problem in Cython that could be worked around for memoryviews, but in general the lack of a Cython runtime is a blessing for distribution purposes and a wart for most other purposes.
This seems easy to fix - a Cython runtime would be a python module like cython.runtime that Cython modules imported and used, right? You could emulate this perfectly by just checking for such a module in sys.modules at import time, and injecting a copy if none was found. (With some versioning in the name so modules compiled with different versions of Cython could coexist.) This would be much easier than coming up with elaborate object model hacks, since it just uses existing standard python mechanisms... -n
_______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
