> 2011/11/9 Francois Bissey <francois.bis...@canterbury.ac.nz>: > > Maybe setting MPMATH_NOGMPY is not enough to prevent it to > call to gmpy "init" function that calls mp_set_memory_functions. > > I will try to debug a bit further, in the worst case, I can resubmit a > sagemath package with "Conflicts: python-gmpy". I had it for a long > time with "Conflicts: python-numpy" when using the patch to use > sympy version of mpmath... With the conflicts rpm information, it > asks the user for removal of the package unless using some > "--force" like option (actually, usually --nodeps). > I already complained to mpmath upstream that they have added some code that looks for sage even if MPMATH_NOSAGE is set, it could be that something similar has been done with gmpy.
Upstream listened to my request favorably but we may have to contribute the bits. I'll search my home inbox for it. There was some good suggestions on what to do. Francois This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org