On Wed, Jul 03, 2013 at 04:33:50PM -0600, Ondřej Čertík wrote: > I haven't thought about this before, but you are right. If we start > depending on mpmath as an external project, then we have to test all > versions that we decide to support. So that's a major pain and that is > a great argument why we should include a version of mpmath in sympy > and making sure that this particular version works great with sympy on > all platforms and Python versions.
Why we can't just depend on this particular version of mpmath? If it has a stable api and if it's well supported - what's a difference? It's hardly a reason to include a bundled copy... > I stated all the reasons why we should include it in sympy in my > previous emails. If your only reason against is "nothing special", in > my opinion that's not good enough reason to make life more complex to > a lot of our users. I think the major reasons for unbundling of mpmath are the reasons why few programs ship their own libraries. Nothing special. Your reasons are applicable to any external dependency of sympy. The only difference: mpmath is not optional. > That's if you use virtualenv. Many times I install from tar.gz or git, > and many times offline. It seems to be not very common setups. Especially, an offline setup with git... > Other users install .exe on Windows. Why we can't include mpmath here (but from external source)? > Anyway, I think the conclusion is clear -- make it so that sympy can > use external mpmath, then we'll go from there. I don't see why we can't decide now whether we want include a copy of mpmath or not, but reiterate again... -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
