Updates:
Summary: Removing sorting of Add.args and Mul.args
Comment #3 on issue 2855 by asmeu...@gmail.com: Removing sorting of
Add.args and Mul.args
http://code.google.com/p/sympy/issues/detail?id=2855
A better solution might be to remove all sorting entirely. Hash
randomization
Updates:
Blockedon: sympy:3272
Comment #4 on issue 2855 by asmeu...@gmail.com: Removing sorting of
Add.args and Mul.args
http://code.google.com/p/sympy/issues/detail?id=2855
(No comment was entered for this change.)
--
You received this message because you are subscribed to the
Issue 3272: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
This issue is now blocking issue sympy:2855.
See http://code.google.com/p/sympy/issues/detail?id=2855
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Issue 2855: Removing sorting of Add.args and Mul.args
http://code.google.com/p/sympy/issues/detail?id=2855
This issue is now blocking issue sympy:1973.
See http://code.google.com/p/sympy/issues/detail?id=1973
--
You received this message because you are listed in the owner
or CC fields of this
Updates:
Blockedon: sympy:2855
Comment #15 on issue 1973 by asmeu...@gmail.com: hash(Integer) should
return the int
http://code.google.com/p/sympy/issues/detail?id=1973
I think we have to change how __eq__ works to fix this. See issue 2855, for
at least one (radical) solution.
--
Comment #35 on issue 274 by asmeu...@gmail.com: evaluate keyword from old
core
http://code.google.com/p/sympy/issues/detail?id=274
Another issue I just noticed with evaluate=False. It will make solving
issue 2855 (and as a consequence issue 1973) very difficult if not
impossible to fix.
Updates:
Blockedon: sympy:274
Comment #6 on issue 2855 by asmeu...@gmail.com: Removing sorting of
Add.args and Mul.args
http://code.google.com/p/sympy/issues/detail?id=2855
(No comment was entered for this change.)
--
You received this message because you are subscribed to the
Issue 274: evaluate keyword from old core
http://code.google.com/p/sympy/issues/detail?id=274
This issue is now blocking issue sympy:2855.
See http://code.google.com/p/sympy/issues/detail?id=2855
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Comment #17 on issue 3272 by asmeu...@gmail.com: Python 3.3 test failures
http://code.google.com/p/sympy/issues/detail?id=3272
A bit of good news: I just tested Python 3.3b1, and the doctests no longer
crash, thanks to Ronan's patch. A big thanks for that.
--
You received this message
Comment #5 on issue 3022 by mario.pe...@gmail.com: maximum recursion depth
exceeded with expand(complex=True)
http://code.google.com/p/sympy/issues/detail?id=3022
test_issue_3022 behaves erratically on my computer Linux 3.0.0-1-amd64
SymPy commit 9ba3cb3eb92fa5a5b6a75e11890b44a4a5676cf4 ,
Comment #6 on issue 3022 by asmeu...@gmail.com: maximum recursion depth
exceeded with expand(complex=True)
http://code.google.com/p/sympy/issues/detail?id=3022
This is because of hash randomization. See the recent discussion on the
mailing list. The problem is the widely varied output from
11 matches
Mail list logo