[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Serhiy Storchaka added the comment: New changeset 5659743b5693c9e23313a74117948294e35013f4 by Serhiy Storchaka (Miss Islington (bot)) in branch '3.6': bpo-32365: Fix a reference leak when compile __debug__. (GH-4916) (#4918)

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Roundup Robot : -- pull_requests: +4813 ___ Python tracker ___

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Serhiy Storchaka added the comment: New changeset bd6ec4d79e8575df3d08f8a89ba721930032714c by Serhiy Storchaka in branch 'master': bpo-32365: Fix a reference leak when compile __debug__. (#4916)

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Serhiy Storchaka : -- pull_requests: +4811 ___ Python tracker ___ ___

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Serhiy Storchaka : -- dependencies: -Build-out an AST optimizer, moving some functionality out of the peephole optimizer resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.6

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Serhiy Storchaka added the comment: New changeset b82da9ebb20053637e731fd40589e1e52f9f8f6e by Serhiy Storchaka in branch '3.6': [3.6] bpo-27169: The __debug__ constant is now optimized out at compile time. (GH-4880) (#4882)

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Serhiy Storchaka : -- pull_requests: +4778 ___ Python tracker ___ ___

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Serhiy Storchaka added the comment: New changeset 3325a6780c81f1ea51190370b5454879c4862a37 by Serhiy Storchaka in branch 'master': bpo-27169: The __debug__ constant is now optimized out at compile time. (#4880)

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Serhiy Storchaka : -- keywords: +patch pull_requests: +4774 stage: needs patch -> patch review ___ Python tracker

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Neil Schemenauer : -- nosy: +nascheme ___ Python tracker ___ ___

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Serhiy Storchaka : -- dependencies: +Build-out an AST optimizer, moving some functionality out of the peephole optimizer ___ Python tracker

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Change by Serhiy Storchaka : -- assignee: -> serhiy.storchaka stage: -> needs patch type: -> behavior versions: +Python 3.7 -Python 3.6 ___ Python tracker

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Josh Rosenberg added the comment: 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

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

Serhiy Storchaka added the comment: I think that the complete solution of this problem is making __debug__ a named constant like None, True, False. This needs changing the grammar of Python. -- nosy: +serhiy.storchaka ___ Python tracker

[issue27169] __debug__ is not optimized out at compile time for anything but `if:` and `while:` blocks

New submission from Josh Rosenberg: Issue #22091 points out a quirk in the compile function and use of the __debug__ "constant" causing inconsistent behavior when the optimize level of the compile call differs from that of the main interpreter; __debug__ in an `if` or `while` statement is