[issue34464] There are inconsitencies in the treatment of True, False, None, and __debug__ keywords in the docs

Stéphane Wirtel added the comment: @serhiy The issue about the assigment operator is closed https://bugs.python.org/issue36052 could we close this issue? thank you -- ___ Python tracker

[issue34464] There are inconsitencies in the treatment of True, False, None, and __debug__ keywords in the docs

Change by R. David Murray : -- versions: -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34464] There are inconsitencies in the treatment of True, False, None, and __debug__ keywords in the docs

Serhiy Storchaka added the comment: __debug__ is not a keyword. And the error message has been changed in 3.8. But it is a special enough. You can not use this name in any assignment context: >>> __debug__ = 1 File "", line 1 SyntaxError: cannot assign to __debug__ >>> for __debug__ in []:

[issue34464] There are inconsitencies in the treatment of True, False, None, and __debug__ keywords in the docs

Stéphane Wirtel added the comment: Hi @David, Maybe we could remove 3.6 from the list because 3.6 is in security mode and not bugfix. Is there a security issue with this bug? -- nosy: +matrixise ___ Python tracker

[issue34464] There are inconsitencies in the treatment of True, False, None, and __debug__ keywords in the docs

R. David Murray added the comment: I've removed 2.7 since those constants are not keywords in 2.7 (although None and __debug__ do raise syntax errors even in 2.7, they are not keywords there). Which is almost certainly why the docs treat them inconsistently (leftovers from before they