No current sage dev knows pynac code, and it is a can of worms. All of the following are worrysome tickets:
https://trac.sagemath.org/ticket/30688 https://trac.sagemath.org/ticket/31411 https://trac.sagemath.org/ticket/31337 At some point pynac and ginac diverged, and while ginac continues to be maintained and developed, we cannot draw on the expertise there. Any obvious ways to replace pynac with something that works and does not contain crazy C++ undocumented stuff? On Wed, Feb 17, 2021 at 10:39 AM Emmanuel Charpentier <emanuel.charpent...@gmail.com> wrote: > > I forgot the link to the ticket... > > Le mercredi 17 février 2021 à 11:30:47 UTC+1, Emmanuel Charpentier a écrit : >> >> A question on ask.sagemath.org showed a bug leading to situations where >> foo.expand() is mathematically different of foo, which seems both >> sufficiently frequent and sufficiently nasty to warrant calling your >> attention to it. >> >> This may be in pynac territory, where I am unable to help you... > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/18920b2d-7cba-4a54-ad72-6526cbea3ba0n%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq0U1AGiikdhuGK4n-t6TmoCDDC0Ky4wV_B5%3DqwBK1r1OQ%40mail.gmail.com.
