Benjamin Peterson [EMAIL PROTECTED] added the comment:
Solved by r64121.
--
resolution: - fixed
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
A clean solution is now proposed in #3021.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
___
___
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
superseder: - Lexical exception handlers
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
___
___
Changes by Adam Olsen [EMAIL PROTECTED]:
--
nosy: +Rhamphoryncus
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
___
___
Python-bugs-list mailing
Antoine Pitrou [EMAIL PROTECTED] added the comment:
This is a complementary patch that should fix the remaining cases
(funnily doctest was relying on the old behaviour).
Unfortunately #2833 still remains, and would probably need some
discussion on the ML for proper resolution.
Added file:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
For time being, should r62847 be reverted?
--
nosy: +benjamin.peterson
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
Antoine Pitrou [EMAIL PROTECTED] added the comment:
I don't think so. As Amaury pointed in #2833, the original re-raising
behaviour which got changed by fixing the present bug was rather broken
in its own way.
Anyway, I think the question better be asked on the ML because any
solution for the
Changes by Antoine Pitrou [EMAIL PROTECTED]:
Removed file: http://bugs.python.org/file10424/better_exc_cleanup.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Patch removed, there are still some unsolved cases :-)
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Here is a hopefully complete patch using the same approach as before.
However I'm now convinced that another approach would be better in order
to solve both this bug and the various re-raising issues. It would
involve replacing most of the
Antoine Pitrou [EMAIL PROTECTED] added the comment:
This bug should be reopened, the patch does not fix it when the except
clause does not assign the exception to a local variable (that is,
except KeyError rather than except KeyError as e).
Another can of worms also appeared in #2833...
Changes by Collin Winter [EMAIL PROTECTED]:
--
assignee: collinwinter -
resolution: fixed -
status: closed - open
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
Antoine Pitrou [EMAIL PROTECTED] added the comment:
No, I don't.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Python-bugs-list mailing list
Unsubscribe:
Antoine Pitrou [EMAIL PROTECTED] added the comment:
Here is a last patch fixing without lines longer than 78 chars.
Added file: http://bugs.python.org/file10213/exc_cleanup4.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
Barry A. Warsaw [EMAIL PROTECTED] added the comment:
r62847
--
priority: release blocker - critical
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
Collin Winter [EMAIL PROTECTED] added the comment:
Looks good to me. Antoine, do you have commit privileges?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Changes by Georg Brandl [EMAIL PROTECTED]:
--
priority: critical - release blocker
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Python-bugs-list mailing
Antoine Pitrou [EMAIL PROTECTED] added the comment:
A new patch with just an updated comment in ceval.c.
Added file: http://bugs.python.org/file10171/exc_cleanup3.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
Barry A. Warsaw [EMAIL PROTECTED] added the comment:
Knocking the priority down to critical for the next alpha release. This
can be readdressed once the release is made.
--
nosy: +barry
priority: release blocker - critical
__
Tracker [EMAIL PROTECTED]
New submission from Antoine Pitrou [EMAIL PROTECTED]:
See http://mail.python.org/pipermail/python-3000/2008-March/012830.html
: the exception state can survive across thread switches if the
enclosing frame is not destroyed immediately.
--
components: Interpreter Core
messages: 64697
Antoine Pitrou [EMAIL PROTECTED] added the comment:
And this is a patch, together with a test.
--
keywords: +patch
Added file: http://bugs.python.org/file9889/exc_cleanup.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
Changes by Christian Heimes [EMAIL PROTECTED]:
--
priority: - release blocker
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
__
___
Python-bugs-list mailing list
Jeffrey Yasskin [EMAIL PROTECTED] added the comment:
Thanks for the patch. This isn't specific to threads at all, so the test
doesn't need to spawn a thread, just raise an exception from a nested
function with a parameter, catch it, delete the object the parameter
referred to, and then check
Antoine Pitrou [EMAIL PROTECTED] added the comment:
You are right, threads aren't needed. So, attaching an updated patch.
Added file: http://bugs.python.org/file9898/exc_cleanup2.patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2507
24 matches
Mail list logo
