On 12/20/2012 01:02 PM, Burcin Erocal wrote:
What should I do ? Unconditionally include the cython interface to
the sage library, and mark all doctests as optional ?
Can you compile the Cython interface without the header files installed
by your package?
No
I assume the Cython interface needs to be changed whenever you update
your library.
Yes, but changing spkg versions requires a ticket, on which the sage
library can also be changed.
Which Sage version is used with an experimental package
cannot be controlled, since Sage just grabs the latest version available
at install time. Hence, if you keep the interface separate from
the spkg, you will run into many incompatibility issues.
OK. But then how do the other spkgs do ?
Wouldn't it be easier to include the Cython interface in the package?
AFAIK, Cython's build system improved significantly and there is no
reason to use Sage's build system for a Cython module.
Is it possible to patch the sage library when installing an spkg ? What
if the patch fails because the sage library was updated since the last
spkg updatye ??? This seems like asking for trouble, and incompatibilities.
I still don't understand how it is currently done.
Charles
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
