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 gregory.p.smith
Recipients Rotem Yaari, Yury.Selivanov, georg.brandl, gregory.p.smith, gvanrossum, larry, ncoghlan, oconnor663, serhiy.storchaka, vstinner, yselivanov
Date 2016-06-12.01:16:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465694219.79.0.211166010184.issue25782@psf.upfronthosting.co.za>
In-reply-to
Content
Patch review: I see two competing solutions with differing behaviors. 

Yury's raises a RuntimeError in the loop situation.

Serhiy's simply reorders the exception context to put the referred to one at the front of the chain in the event of a loop.

The 3.5 Release manager or someone familiar with the contextlib ExitStack code where this is triggered should make the decision as to the best way to fix this.

(I came to this bug via the ExitStack + subprocess issue27122 which merely has a suggested workaround patch as a band aid that might help until this is fixed)
History
Date User Action Args
2016-06-12 01:17:00gregory.p.smithsetrecipients: + gregory.p.smith, gvanrossum, georg.brandl, ncoghlan, vstinner, larry, Yury.Selivanov, serhiy.storchaka, yselivanov, oconnor663, Rotem Yaari
2016-06-12 01:16:59gregory.p.smithsetmessageid: <1465694219.79.0.211166010184.issue25782@psf.upfronthosting.co.za>
2016-06-12 01:16:59gregory.p.smithlinkissue25782 messages
2016-06-12 01:16:59gregory.p.smithcreate