On Fri, Aug 02, 2013 at 10:36:48PM -0700, Robert Bradshaw wrote: > > its bearable, and it's just automake. manually created makefiles are not > > affected. why does cython use .pyx for two different things? what would > > be the canonical extension for C++ cython files? i've chosen to use .pyxx, > > any better options? > > Though there are some features only available with C++, I don't > consider this "two different things" as the similarities far, far > outweigh the differences.
well, there are two build chains .pyx->.c->.so and .pyx->.cc->.so. without additional information, you cannot tell how to resolve .pyx->.so. usually (outside distutils) there's a tendency towards using different suffixes for different purposes. > To expand on what Stefan wrote, distutils automatically figures out > the flags, linker options, headers, etc. to make an extension > compatible with that specific Python on your system, which one would > either have to do manually or "extract" from distutils otherwise. this has already been implemented (outside and without and before distutils). see [1] for how it may work for python extensions. it a bit beyond the scope of cython and really beyond the scope of my proposed patch. regards felix [1] www.gnu.org/software/automake/manual/html_node/Python.html _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel