Comment #11 on issue 1949 by mattpap: Doctests for polynomials module http://code.google.com/p/sympy/issues/detail?id=1949
This issue is not related strictly to ground types, but a bit was said about this here, so lets summarize recent changes in polys11 related to ground types.
Previously we had three classes of ground types: sympy, python, gmpy. sympy ground types worked always and were independent of Python version or external libraries. They were slow and caused doctest failures because SymPy doesn't keep types of objects in general. python ground types were much faster but required Python 2.6 to support rational numbers (fall back was sympy ground type). gmpy ground types were the fastest but required an external library.
The new approach is to keep gmpy ground types, but change python ground types and remove sympy ground types. In e50346d20c0c0af2e01a86384708f73f9a8ceab4 in polys11 branch I reimplemented Fraction as PythonRationalType, which doesn't use abstract base classes, so doesn't require Python 2.6 and is faster than Fraction. This way python ground types don't require fall back any more, so sympy ground types are now useless. They weren't removed entirely and you can still run SymPy with SYMPY_GROUND_TYPES=sympy, but I don't consider using this configuration for anything besides experimentation during development of polys module.
Both python and gmpy ground types strictly keep types, so all doctests now pass (up to the problems with Python 2.6.6) and all tests pass also with Python 2.4-2.7. It's now sufficient to only test python and gmpy ground types. This reduces testing time and makes running doctests robust (always up to 2.6.6).
-- You received this message because you are subscribed to the Google Groups "sympy-issues" group. To post to this group, send email to sympy-iss...@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.
