[issue1686386] Python SEGFAULT on tuple.__repr__ and str()

2007-09-30 Thread Brett Cannon
Brett Cannon added the comment: And fixed in r58289. _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue1686386] Python SEGFAULT on tuple.__repr__ and str()

2007-09-30 Thread Brett Cannon
Brett Cannon added the comment: Applied in r58288. If I did something stupid or people don't want the overhead they can yell at the commit. =) -- resolution: -> fixed status: open -> closed _ Tracker <[EMAIL PROTECTED]>

[issue1686386] Python SEGFAULT on tuple.__repr__ and str()

2007-09-20 Thread Georg Brandl
Georg Brandl added the comment: I don't have a specific opinion on this; the usage of Py_EnterRecursiveCall/Py_ReprEnter certainly looks correct. -- assignee: georg.brandl -> brett.cannon _ Tracker <[EMAIL PROTECTED]>

[issue1686386] Python SEGFAULT on tuple.__repr__ and str()

2007-09-17 Thread Brett Cannon
Changes by Brett Cannon: -- status: pending -> open _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list mailing list Unsubscribe:

[issue1686386] Python SEGFAULT on tuple.__repr__ and str()

2007-09-13 Thread Thomas Herve
Thomas Herve added the comment: I think it could be solved both the same way: if tuple repr is wrong, there are probably some other repr code that is wrong too, so fixing PyObject_Repr is safer. _ Tracker <[EMAIL PROTECTED]>

[issue1686386] Python SEGFAULT on tuple.__repr__ and str()

2007-09-12 Thread Brett Cannon
Changes by Brett Cannon: -- title: Python SEGFAULT on invalid superclass access -> Python SEGFAULT on tuple.__repr__ and str() _ Tracker <[EMAIL PROTECTED]> _ _