> > While this might work for simple projects, this won't work when you need > the metadata that cythonize() adds. For example, anything using > cysignals really must use cythonize(), it won't work otherwise. >
Jeroen, As of Cython 0.22, it looks like the metadata you refer to is cached in the Cython-generated C files: http://grokbase.com/t/python/cython-devel/152c310vvz/cython-cython-0-22-released Specifically, if you look at the top of a Cython-generated C file, there is what looks to be a JSON string encoding the metadata. Of course, as Erik says one shouldn't have to mess with this all "by hand". For example, setuptools could provide a "stub" version of cythonize that (a) does nothing but load this metadata if the C files are up to date and otherwise (b) attempts to import Cython and run the real cythonize... Best, Nathan -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
