[issue2833] __exit__ silences the active exception

2008-06-11 Thread Benjamin Peterson 

Benjamin Peterson [EMAIL PROTECTED] added the comment:

Fixed in r64121.

--
nosy: +benjamin.peterson
resolution:  - fixed
status: open - closed

___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-06-01 Thread Antoine Pitrou 

Antoine Pitrou [EMAIL PROTECTED] added the comment:

A clean solution to both #2507 and #2833 is now proposed in #3021.

___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-06-01 Thread Benjamin Peterson 

Changes by Benjamin Peterson [EMAIL PROTECTED]:


--
superseder:  - Lexical exception handlers

___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-14 Thread Antoine Pitrou 

Antoine Pitrou [EMAIL PROTECTED] added the comment:

Small typo in the snippet above, this should obviously read:

   try:
  raise Exception(foo)
   except Exception as e:
  try: raise KeyError(caught)
  except KeyError: pass
  raise e

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-14 Thread Antoine Pitrou 

Antoine Pitrou [EMAIL PROTECTED] added the comment:

As Amaury said, lexically nested exception handlers make re-raising
behaviour buggy. In Py3k, a workaround is to instead write:

   try:
  raise Exception(foo)
   except Exception as :
  try: raise KeyError(caught)
  except KeyError: pass
  raise e

With the slight inconvenience that the raise e line will be appended
to the original traceback.

If we want bare raise statements to work as expected after a nested
exception handler, we'll need to add proper exception stacking, for
example by adding the exception value as a member of PyTryBlock. The
effect on performance should also be measured.

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-13 Thread Antoine Pitrou 

Changes by Antoine Pitrou [EMAIL PROTECTED]:


--
nosy: +pitrou

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-13 Thread Amaury Forgeot d'Arc 

Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:

Note that the problem is not related to with, but with nested
exception handlers:

try:
raise Exception(foo)
except:
try: pass
except: pass
raise # in Py2.5 throws 'foo', in Py3.0 fails with RuntimeError


OTOH, python has always had poor support for nested exceptions; tried
with python24 and python25::

   try:
raise Exception(foo)
   except:
  try: raise KeyError(caught)
  except KeyError: pass
  raise # reraise the KeyError...

This does not happen if the two lines with KeyError are moved in another
function.

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-13 Thread Antoine Pitrou 

Antoine Pitrou [EMAIL PROTECTED] added the comment:

I've just discovered that the patch in r62847 doesn't clean up the
exception state if the except clause does not mention a local variable,
e.g. except MyException instead of except MyException as e.

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-13 Thread Georg Brandl 

Georg Brandl [EMAIL PROTECTED] added the comment:

Raising priority.

--
nosy: +georg.brandl
priority:  - release blocker

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-12 Thread Dmitry Dvoinikov 

New submission from Dmitry Dvoinikov [EMAIL PROTECTED]:

If a context manager is used within exception handling block, the active
exception is silenced after the context block completes and __exit__ exits.

try:
raise Exception(foo)
except:
with SomeContextManager():
pass
raise # in Py2.5 throws 'foo', in Py3.0 fails with RuntimeError

--
components: Interpreter Core
messages: 66713
nosy: ddvoinikov
severity: normal
status: open
title: __exit__ silences the active exception
type: behavior
versions: Python 3.0

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue2833] __exit__ silences the active exception

2008-05-12 Thread Amaury Forgeot d'Arc 

Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:

This problem was introduced by r62847.

--
nosy: +amaury.forgeotdarc

__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2833
__
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com