Hi Dima, On 2018-09-29, Dima Pasechnik <dimp...@gmail.com> wrote: > I believe making libGAP the default GAP interface is the way to go, and > much of the work needed for this conversion is already done... > > libgap's GAP objects are just thin cython wrappers around GAP's objects in > memory. > So you basically need to send to libgap a complete valid GAP statement > defining G.
Sure. I was afraid that in some situations I'd need to convert from gap-pexpect to libgap (e.g., when unpickling cohomology rings that I've computed in the past). However, unpickling of gap stuff is done in a custom way anyway -- so, in my unpickling functions I could simply replace gap by libgap. It is some work, but hopefully worth-while to do. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
