[Python-Dev] Another PEP 343 contextmanager glitch
Guido van Rossum
guido at python.org
Sat Mar 25 00:05:46 CET 2006
More information about the Python-Dev mailing list
Sat Mar 25 00:05:46 CET 2006
- Previous message: [Python-Dev] Another PEP 343 contextmanager glitch
- Next message: [Python-Dev] Another PEP 343 contextmanager glitch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Oops, that's definitely a bug. Please go ahead and fix in both places. (I'm still trying to fathom the other PEP 343 issue you brought up.) --Guido On 3/24/06, Phillip J. Eby <pje at telecommunity.com> wrote: > It appears that the contextmanager implementation (both in the stdlib and > as described in the PEP) doesn't correctly handle the case where the > generator yields a new value in response to throw(). It responds by > suppressing the original exception, but IIRC earlier versions of the PEP > threw a RuntimeError for this scenario. > > Unless there are any objections, I'd like to restore this by replacing the > "return True" that follows the throw(), with: > > raise RuntimeError("generator didn't stop after throw()") > > and again, update the PEP accordingly. > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] Another PEP 343 contextmanager glitch
- Next message: [Python-Dev] Another PEP 343 contextmanager glitch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list