The following code, which works with the upstream version of SymPy, is broken under Gentoo: import sympy.mpmath This is due to modifications made downstream in the Gentoo ebuild to defer to the systemwide mpmath package. While this is a good thing it needs to be done in a way that does not break existing code. (There are extremely good reasons for preferring to import mpmath via sympy.mpmath rather than as a standalone package; specifically due to issues which can arise when SymPy is using its bundled version and application code is using a standalone version.)
(In reply to Freddie Witherden from comment #0) > done in a way that does not break existing code. (There are extremely good > reasons for preferring to import mpmath via sympy.mpmath rather than as a > standalone package; specifically due to issues which can arise when SymPy is > using its bundled version and application code is using a standalone > version.) could you give examples of the "extremely good reasons" where sympy.mathmp is prefered over mathmp, and why not convincing upstream to use stock mathmp?
(In reply to Sébastien Fabbro from comment #1) > could you give examples of the "extremely good reasons" where sympy.mathmp > is prefered over mathmp, and why not convincing upstream to use stock mathmp? See: http://osdir.com/ml/sympy/2013-04/msg00386.html where the error was due to SymPy using its own version of mpmath and my script importing mpmath directly. Given that development work on mpmath has started up again it is likely that SymPy will eventually stop bundling mpmath. However, as it stands at the moment, SymPy does bundle mpmath. Further, there are applications which depend on this functionality (as in being able to import mpmath via the above route).
+ 06 Feb 2014; Sébastien Fabbro <bicatali@gentoo.org> sympy-0.7.4.1.ebuild: + Reintroduce use flag system-mpmath to allow using bundled mpmath, bug #500284 +
