Comment #13 on issue 2482 by vlada.pe...@gmail.com: Stop bundling mpmath http://code.google.com/p/sympy/issues/detail?id=2482
First of all, I have to say that I don't consider ease of porting to Py3 a major argument. Yes, it makes things a little easier, but as Aaron said, I can work around it if I have to. (Re #8: Absolutely, I even estimated I'd have to contribute upstream during my project, most likely for PyPy when we get there. However, I would do this only as a last resort, as it's a slow process. For example: I contribute to distribute -> 2 months later they have a release -> 6-8 months after that distributions pack ---> almost a year has passed)
However, I don't see the installation argument as a strong one either. If you don't have root access to your computer, then you're running SymPy from source anyway, so you might as well just download one more package and put it there. Otherwise, there's pip and that's as easy as it gets. The same applies for Windows - you're either running from source (and can download two tarballs instead of one), or you've installed SymPy already (and hence know how to install Python packages). Ok, perhaps I'm a bit wrong here, I don't use Windows for development. :) And, as Frederik said in #12, we could provide a bundled and non-bundled version; with relative imports it will work easily enough.
I think the major reason for unbundling of mpmath is the reason few programs ship their own libraries: faster (security) updates to users. So, the user doesn't have to wait for a release of SymPy to use some new feature of mpmath. Finally, as Frederik said, mpmath has been stable for a while now and will remain stable.
-- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to sympy-issues@googlegroups.com. To unsubscribe from this group, send email to sympy-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy-issues?hl=en.
