➜

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 ncoghlan
Recipients Alexander.Jones, DLitz, Martin Blais, blais, daniel.urban, eric.araujo, georg.brandl, giampaolo.rodola, hniksic, michael.foord, ncoghlan, piotr.dobrogost, pitrou, r.david.murray, rhettinger, vstinner
Date 2016-11-19.12:23:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479558186.99.0.210816652081.issue10049@psf.upfronthosting.co.za>
In-reply-to
Content 
No, it wouldn't, as ExitStack() does far more than merely implement a null context.

It would be like adding "nulliterable = ()" as a builtin, rather than just telling people "If you need a null iterable, use an empty tuple".
History
Date User Action Args
2016-11-19 12:23:07ncoghlansetrecipients: + ncoghlan, georg.brandl, rhettinger, blais, pitrou, vstinner, giampaolo.rodola, hniksic, eric.araujo, r.david.murray, michael.foord, daniel.urban, piotr.dobrogost, Alexander.Jones, DLitz, Martin Blais
2016-11-19 12:23:06ncoghlansetmessageid: <1479558186.99.0.210816652081.issue10049@psf.upfronthosting.co.za>
2016-11-19 12:23:06ncoghlanlinkissue10049 messages
2016-11-19 12:23:06ncoghlancreate