I used to forbid gmpy from sage-on-gentoo installs. Because prior to sympy 1.0 (ok may be also the latest 0.7) the backend would interfere with the sage backend and you couldn’t properly disable sage or gmpy. I thought that was definitely fixed in sympy. At least I didn’t get any more report after I allowed it again.
François > On 22/10/2016, at 03:37, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > > On 2016-10-21 16:11, Jeroen Demeyer wrote: >> It consistently shows up while running doctests, but not in an >> interactive Sage session. I have no idea what is going on. > > OK, got it. This problem happens whenever gmpy2 (a package I have been > playing with recently but which is not in Sage) is imported because it > changes the GMP/MPIR memory allocation functions. > > It turns out that the doctester imports sympy to "Disable SymPy terminal > width detection", which imports mpmath, which imports gmpy2. > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
