Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Burcin Erocal
On Thu, 20 Dec 2012 14:10:55 +0100 Charles Bouillaguet wrote: > > I am not suggesting to patch the Sage library when installing your > > package. You can put the interface in a separate Cython module > > which is built by the usual Python/Cython setup.py magic and > > installed in the system pyth

Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Burcin Erocal
Hi Martin, On Thu, 20 Dec 2012 13:15:51 +0100 Martin Albrecht wrote: > > 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. > > my understanding

Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Jeroen Demeyer
On 2012-12-20 14:10, Charles Bouillaguet wrote: > Again, what should I do :) ? The question is really: what to do with *documentation* of optional/experimental packages, should it be amongst the Sage documentation? If YES, then indeed all doctests need to be marked optional. -- You received this

Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Charles Bouillaguet
> I am not suggesting to patch the Sage library when installing your > package. You can put the interface in a separate Cython module which is > built by the usual Python/Cython setup.py magic and installed in the > system python module directory. Then people will be able to import your > module fr

Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Burcin Erocal
On Thu, 20 Dec 2012 13:15:38 +0100 Charles Bouillaguet wrote: > 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

Re: Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Martin Albrecht
> 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. Hi Burcin, my understanding is that Charles was more specifically asking about including his expe

Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Charles Bouillaguet
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 nee

Re: [sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Burcin Erocal
Hi Charles, On Thu, 20 Dec 2012 12:37:33 +0100 Charles Bouillaguet wrote: > I (amongst with others) have written a library that solves boolean > equations in some way. I wanted to include it as an experimental > spkg. I thus wrote a cython interface to Sage. To be usable from > inside Sage, bot

[sage-devel] Correct procedure for an experimental package

2012-12-20 Thread Charles Bouillaguet
Hi all, I (amongst with others) have written a library that solves boolean equations in some way. I wanted to include it as an experimental spkg. I thus wrote a cython interface to Sage. To be usable from inside Sage, both the library itself and the cython interface are necessary. What is the