Status: Accepted
Owner: [email protected]
CC: [email protected]
Labels: Type-Defect Priority-Medium

New issue 2282 by [email protected]: doctests broken by the commit edabb89c5006a7
http://code.google.com/p/sympy/issues/detail?id=2282

The doctests are broken on python 2.7.1 Ubuntu Natty, 64 bit:


$ bin/doctest  sympy/geometry/polygon.py
============================= test process starts ==============================
executable:   /usr/bin/python  (2.7.1-final-0)

sympy/geometry/polygon.py[34] .............................F.... [FAIL]

________________________________________________________________________________
___________________ sympy.geometry.polygon.Triangle.inradius ___________________ File "/home/ondrej/repos/sympy/sympy/geometry/polygon.py", line 18, in sympy.geometry.polygon.Triangle.inradius
Failed example:
    t.inradius
Expected:
    (4*a**2*(a**2)**(1/2) - 2*2**(1/2)*a**2*(a**2)**(1/2))/(8*a**2)
Got:
    -(-4*a**2*(a**2)**(1/2) + 2*2**(1/2)*a**2*(a**2)**(1/2))/(8*a**2)

============= tests finished: 33 passed, 1 failed, in 0.39 seconds =============
DO *NOT* COMMIT!




and this commit broke it:


edabb89c5006a7d6b111f4ba74f55c5833366c53 is the first bad commit
commit edabb89c5006a7d6b111f4ba74f55c5833366c53
Author: Gary Kerr <[email protected]>
Date:   Fri Mar 25 17:10:48 2011 +0000

    Issue 828: fix Polygon docstrings

    I have updated all docstrings in sympy/geometry/polygon.py using
    numpy docstring standard mentioned by Brian Granger on mailing list
    message about broken docs.

    I also added spaces around operators in a few lines of code to improve
    legibility.

:040000 040000 9f4e3d5a7386b06fa45380c06c38785deda480a0 9492184378c7e515fc2d8fce57cef81a3e32ca08 M sympy


--
You received this message because you are subscribed to the Google Groups 
"sympy-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sympy-issues?hl=en.

Reply via email to