That is exactly the case: the cocoalib package is just that for the moment:
a way to install cocoalib from sage.
The plan when that was done was to write a cython interface , but that
hasn't been done yet. Since cocoalib is a very big library, I think it
would be a good idea to do so incrementally: when we locate some
computation that would be best done by cocalib , wrap the specific library
calls that we need for that specific computation, and expose them through
some convenient method. Your case is probably the first one that has
apperaed (cocoalib was added to sage just this summer), so I see it as a
good opportunity to start wrapping cocoalib functions.
Although, it will sure require some work (and maybe some insight from
someone that has experience using cocoalib).
Best,
Miguel
El sábado, 1 de septiembre de 2018, 23:12:26 (UTC+2), Simon King escribió:
>
> PPS:
>
> On 2018-09-01, Simon King <simon...@uni-jena.de <javascript:>> wrote:
> > A user called Tomer has contacted me off-list and pointed to a CoCoALib
> interface
> > (Trac #25707); I didn't know that such (experimental) interface exists.
> CoCoA is
> > well known for efficient Hilbert series computations.
>
> "sage -i cocoalib" does work. However, how would one use it?
> search_src('cocoa') gives no answer, and #25707 gives no example. So,
> is #25707 really providing an interface (as Tomer was claiming) or just
> a package (without interface)? In the latter case: Is the creation of a
> C library of pexpect interface planned?
>
> Best regards,
> Simon
>
>
--
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.
