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 josh.r
Recipients SilentGhost, arigo, eryksun, josh.r, serhiy.storchaka
Date 2016-05-31.21:06:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464728764.53.0.982180239226.issue27169@psf.upfronthosting.co.za>
In-reply-to
Content
That would also work. The argument I'd give in favor of performing a pass that replaces it with a literal True or False is that you don't have update as many places, don't have to worry about missing a place, and you don't have to decide if __debug__ is a reference to True or False, or a new object entirely.

It's just too easy to miss a case where __debug__ should be special and not notice (because optimizations aren't heavily tested for specific byte code outputs or anything), where a missed optimization for the True or False constant is much less likely to go unnoticed.
History
Date User Action Args
2016-05-31 21:06:04josh.rsetrecipients: + josh.r, arigo, SilentGhost, serhiy.storchaka, eryksun
2016-05-31 21:06:04josh.rsetmessageid: <1464728764.53.0.982180239226.issue27169@psf.upfronthosting.co.za>
2016-05-31 21:06:04josh.rlinkissue27169 messages
2016-05-31 21:06:04josh.rcreate