R. David Murray added the comment:
This code fragment doesn't seem to exist any more. Since there's no test case,
I'm going to close this. I presume it is no longer a problem for SymPy, since
there's been no followup.
--
nosy: +brett.cannon, r.david.murray
resolution: - out of date
Aaron Meurer added the comment:
The OP describes how to get the original code. Anyway, the issue was definitely
fixed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14537
___
Aaron Meurer added the comment:
Or do you mean the code in CPython doesn't exist any more?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14537
___
R. David Murray added the comment:
Yes, it appears that the code does not exist in import.c any more.
When I said test case, I meant unit test, sorry.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14537
Serhiy Storchaka added the comment:
I didn't tested this patch with SymPy, but in general it LGTM.
--
assignee: - haypo
nosy: +serhiy.storchaka
stage: - commit review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14537
New submission from Aaron Meurer asmeu...@gmail.com:
Recently, after a small seemingly unrelated refactoring, the SymPy test suite
in Python 3 started dying with Fatal Python error: Cannot recover from stack
overflow.
Here's how to reproduce the error
git clone
Changes by Antoine Pitrou pit...@free.fr:
--
nosy: +haypo
versions: +Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14537
___
___
STINNER Victor victor.stin...@gmail.com added the comment:
It looks like an issue in SymPy, a stack overflow. Why did you report this
issue on CPython bug tracker?
Is there an infinite loop in a recursive function call?
Can you try to get the full Python traceback using faulthandler? Use -X
Aaron Meurer asmeu...@gmail.com added the comment:
We do have a stack overflow, but this should be raising a RuntimeError, not
killing Python. The way it is now, Python dies completely with abort trap 6
(hence the Mac OS X problem report). Sorry if I didn't make this clear in the
OP.
STINNER Victor victor.stin...@gmail.com added the comment:
SymPy uses a C extension, numpy. The problem may be related to numpy. CPython
tries to catch segmentation fault, but when a C extension is used, CPython may
fail to protect your program against stack overflow.
--
Aaron Meurer asmeu...@gmail.com added the comment:
No it does not. SymPy is a pure Python library.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14537
___
STINNER Victor victor.stin...@gmail.com added the comment:
The (first) Python stack overflow occurs at:
---
(gdb) py-bt
Traceback (most recent call first):
File /home/haypo/issue14537/sympy/py3k-sympy/sympy/core/expr.py, line 2531,
in expand
from sympy.simplify.simplify import
12 matches
Mail list logo
