This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author invisibleroads
Recipients benjamin.peterson, invisibleroads
Date 2015-05-06.17:39:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430933940.26.0.918920419058.issue24070@psf.upfronthosting.co.za>
In-reply-to
Content
The behavior may not be surprising from a technical perspective, but it is unintuitive.

I think exceptions inside a with statement should trigger a traceback, unless you are saying that it is the responsibility of the author to catch and raise the exception inside __exit__, which feels to me like a workaround that is specific to parse_args.
History
Date User Action Args
2015-05-06 17:39:00invisibleroadssetrecipients: + invisibleroads, benjamin.peterson
2015-05-06 17:39:00invisibleroadssetmessageid: <1430933940.26.0.918920419058.issue24070@psf.upfronthosting.co.za>
2015-05-06 17:39:00invisibleroadslinkissue24070 messages
2015-05-06 17:39:00invisibleroadscreate