> > > The idea is that cython produces fully compliant C code, so that no > tuning > > of the generated C code is required. Distributing the cythonized c-files > > has the advantage that the installing user does not need cython > installed. > > In sage we have run into trouble with that due to API incompatibilities > > between Py2 and Py3, and it doesn't seem possible to specify the right > > conditionals in the cython file to produce an appropriate c file with > the > > right conditional pieces of code in. > > As far as I remember, snappy deals with that by providing file.py2.c and > file.py3.c. Nathan could infirm/confirm. >
For SnapPy itself, we don't hit this API issue and so there is just a single version of each Cython-generated ".c" file. For CyPari, I believe Marc Culler did have to use the scheme Vincent mentions above. 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.
