[issue34850] Emit a syntax warning for "is" with a literal
Change by Bachsau : -- nosy: -Bachsau ___ Python tracker <https://bugs.python.org/issue34850> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34850] Emit a syntax warning for "is" with a literal
Bachsau added the comment: This is bullshit. SyntaxWarnings should be raised on problems with the *syntax* not for ProgrammerMightBeDumb errors. There are a whole lot of things a programmer not knowing the language could do wrong. But these are syntactically valid expressions and it is not the purpose of a compiler to teach. -- nosy: +Bachsau ___ Python tracker <https://bugs.python.org/issue34850> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35504] `del OSError().characters_written` raises `SystemError`
Bachsau added the comment: Why is it using -1 instead of NULL as the "not-set-indicator"? -1 is a valid python integer, that can be assigned, even if it doesn't make sense in the context, while `None` can not, because it's missing an `__index__` method. -- ___ Python tracker <https://bugs.python.org/issue35504> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35504] `del OSError().characters_written` raises `SystemError`
Change by Bachsau : -- title: `del OSError().characters_written` raises SystemError -> `del OSError().characters_written` raises `SystemError` ___ Python tracker <https://bugs.python.org/issue35504> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35504] `del OSError().characters_written` raises SystemError
New submission from Bachsau : `del OSError().characters_written` raises `SystemError`: "null argument to internal routine" I don't know why anyone should try this in productive code, but since the documentation says, that every `SystemError` should be reported, I'm doing that. My suggestion would be to make that attribute behave like the other ones of `OSError`, e.g. defaulting to `None` and returning to that value on deletion. -- components: Interpreter Core messages: 331876 nosy: Bachsau priority: normal severity: normal status: open title: `del OSError().characters_written` raises SystemError versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue35504> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com