Georg Brandl added the comment:
Brett, you recently fixed an infinite recursion crasher, right?
--
assignee: - brett.cannon
nosy: +brett.cannon
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1686386
_
Brett Cannon added the comment:
So the first example (in msg31624) crashes because of infinite recursion
with the repr of exceptions::
#7771 0x00065178 in BaseException_repr (self=0x5dc6b8) at
Objects/exceptions.c:128
#7772 0x0001d90c in PyObject_Repr (v=0x5dc6b8) at Objects/object.c:362
#7773
Changes by Brett Cannon:
--
versions: +Python 2.6
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1686386
_
___
Python-bugs-list mailing list
Unsubscribe:
Brett Cannon added the comment:
OK, so I have attached a possible patch. I found out that
tuple.__repr__ didn't do anything to prevent infinite recursion since
you can't pull it off from Python code. But obviously C code is another
matter. =)
Same goes for object.__str__; it didn't think
Thomas Herve added the comment:
object.c is already inconsistent about tabs and space :). It may be
better to fix it in the commit, not to clutter the patch. But I can
provide a new patch if necessary.
_
Tracker [EMAIL PROTECTED]
toxik added the comment:
Hm, may be so.
Feel free to change title/severity if you'd like to.
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1686386
_
___
toxik added the comment:
Minor note: The patch mixes tabs and spaces. AFAIK, PEP 7 says to use
four spaces when making new code, and follow suite in legacy, or convert it.
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1686386
