Updates:
Labels: -NeedsReview
Comment #27 on issue 2041 by Vinzent.Steinberg: Doctest failures in Python
2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
Your patch indeed fixes the problem occuring in Python 2.5.
I get other (probably 64-bit related) failures however:
Comment #28 on issue 2041 by matt...@gmail.com: Doctest failures in Python
2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
I have addressed doctest failures in wester.txt in polys12, so you don't
have to worry about this.
--
You received this message because you are subscribed
Updates:
Status: Fixed
Comment #29 on issue 2041 by ronan.l...@gmail.com: Doctest failures in
Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
I've pushed it in. Note that I still get a few failures in secondquant,
just like Chris reported in
Updates:
Labels: NeedsReview
Comment #26 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
I have cherry-picked the commit from comment 16 of issue 1587 onto this
branch. Please review.
Note, the problem that that
Issue 2041: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
This issue is now blocking issue 1379.
See http://code.google.com/p/sympy/issues/detail?id=1379
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Comment #20 on issue 2041 by smichr: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
FWIW, all but 1 doctest pass under windows. The one that doesn't pass is
the evalf.txt line:
N(fibonacci(1000) - (GoldenRatio)**1000/sqrt(5), strict=True)
which
Comment #21 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
I am currently in the process of updating mpmth, so see if that still fails
after that.
--
You received this message because you are subscribed to the Google Groups
Comment #22 on issue 2041 by Vinzent.Steinberg: Doctest failures in Python
2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
The failing doctest is apparently correlated to the failing test in issue
2110.
--
You received this message because you are subscribed to the Google
Updates:
Labels: NeedsReview asmeurer
Comment #23 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
This was not too hard to fix. I basically had to do what I said in comment
11: I took the code that was changed in that
Comment #17 on issue 2041 by Vinzent.Steinberg: Doctest failures in Python
2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
or was, but I think it still is, I just hit some bug couple days ago
about two files having the same name
What about rather fixing this upstream than
Comment #18 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
The thing is that the thing that created the problem was a fix upstream.
They might not want to change it back. See comment 9.
--
You received this message because
Comment #19 on issue 2041 by Vinzent.Steinberg: Doctest failures in Python
2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
Actually, I was referring to py.test. On Python upstream, I agree with you,
this is probably a lost cause. :)
--
You received this message because you are
Comment #14 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
It looks like Python 2.7.1 has also inherited this problem.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to
Comment #15 on issue 2041 by Vinzent.Steinberg: Doctest failures in Python
2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
Acknowledged.
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this group, send email to
Comment #13 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
As long as we can make it work in all Pythons, I think that's a fine
solution (though I think that further patching doctest is also a fine
solution).
Another thing
Comment #12 on issue 2041 by ronan.l...@gmail.com: Doctest failures in
Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
I don't much like the idea of monkeypatching or reimplementing the stdlib.
Ultimately, I think we should probably just suck it up and accept the idea
Comment #9 on issue 2041 by ronan.l...@gmail.com: Doctest failures in
Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
After stepping through the code in WinPdb, I've identified the source of
our problems. It is this commit:
Comment #10 on issue 2041 by Vinzent.Steinberg: Doctest failures in Python
2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
So, what do we do?
Either we have to find a work-around or to bug upstream until they release
a fixed Python 2.6, I'd say.
--
You received this message
Comment #11 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
We already have a chunk of the Python doctest runner copied and modified
over into our doctest runner (compare our sympy/utilities/runtests.py with
Comment #5 on issue 2041 by andy.terrel: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
Is the Mac the only place this has been observed?
--
You received this message because you are subscribed to the Google Groups
sympy-issues group.
To post to this
Comment #7 on issue 2041 by ondrej.certik: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
I just installed 2.6.6 on linux and all tests pass, and these doctests fail
(see the attachement).
Attachments:
log 27.5 KB
--
You received this
Comment #8 on issue 2041 by ondrej.certik: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
So I think this is not Mac related and we have a problem to solve. :)
--
You received this message because you are subscribed to the Google Groups
sympy-issues
Comment #2 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
Well yes, we could fix it by patching doctest, but to me, something very
strange is going on and we should figure out what it is.
Can someone else maybe verify my
Comment #4 on issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
Maybe for the match one, but the one that is so strange is the
AssumptionsContext() vs. AssumptionsContext([]). Even
typing global_assumptions in the Python 2.6.6
Status: Accepted
Owner: asmeurer
Labels: Type-Defect Priority-Critical Milestone-Release0.7.0 Documentation
New issue 2041 by asmeurer: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
See
Comment #1 on issue 2041 by smichr: Doctest failures in Python 2.6.6
http://code.google.com/p/sympy/issues/detail?id=2041
There are two potential ways to fix this:
1) use my equal function (or equivalent) like this:
assert equal(
... e.match(p**q),
... {p_: x + y, q_: x + y})
By
26 matches
Mail list logo
