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 barry, belopolsky, ncoghlan, r.david.murray, rhettinger, skrah, vstinner, zero.piraeus
Date 2013-10-16.23:18:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7fFBL4yDGyDAArszARkFPsC7mRgxXE4Xo2G+edRrGxNaQ@mail.gmail.com>
In-reply-to <1381964579.03.0.753836047659.issue19266@psf.upfronthosting.co.za>
Content
I didn't choose suppress on a whim. I actually agree with Raymond that
ignore reads better when the context manager is used correctly, but
suppress is more consistent with the terminology used in the documentation
(including even PEP 343), *and* I think it is slightly less vulnerable to
people expecting it to mean "don't even raise the exception and continue
with the next statement inside the with block" (aka the "on error resume
next" misinterpretation).

I think suppress reads *well enough* for it to be worth making the switch
in order to gain those other benefits.
History
Date User Action Args
2013-10-16 23:18:19ncoghlansetrecipients: + ncoghlan, barry, rhettinger, belopolsky, vstinner, r.david.murray, skrah, zero.piraeus
2013-10-16 23:18:19ncoghlanlinkissue19266 messages
2013-10-16 23:18:19ncoghlancreate