> however uncomfortable having our releases of our free software seem > obfuscated and difficult to verify for others - the generated c files > are nearly impossible to read. It would be best if everyone worked from > the highest level code, even those who don't plan to do development > themselves.
Another problem is we're using #DEF's for OS-specific code which means we'd need separate source downloads for each OS. Regardless of how this discussion comes out, I think we have consensus that Beta-3 needs to be released as .pyx sources. The code in setup.py which only built from Pyrex when Version=="Trunk" was recently removed. I like the idea of switching to Cython, but I have some hesitation about > including it in our repository. I believe it makes more sense to locate > things like so on the svn server Keep in mind, if the build environment isn't under trunk/pysoy/ then it must be intended to be installed to site-packages One argument in favor of having it install to site-packages is we'll eventually have PySoy "plugin" modules which may need a similar build system. One argument against is this means it's a separate package from PySoy and, thus, replaces a Pyrex as a dependency with this Cython variant. Piet expressed a similar concern than one of mine, that all these projects (PySoy, Sage, etc) keep building Pyrex based branches for the specific needs of their project, when we should be working on one project together. I don't know how pragmatic that is, but that's something to think about.
_______________________________________________ PySoy-Dev mailing list [email protected] http://www.pysoy.org/mailman/listinfo/pysoy-dev
