[issue34850] Emit a syntax warning for "is" with a literal

2019-11-17 Thread Bachsau
Change by Bachsau : -- nosy: -Bachsau ___ Python tracker <https://bugs.python.org/issue34850> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34850] Emit a syntax warning for "is" with a literal

2019-06-09 Thread Bachsau
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

[issue35504] `del OSError().characters_written` raises `SystemError`

2018-12-14 Thread Bachsau
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

[issue35504] `del OSError().characters_written` raises `SystemError`

2018-12-14 Thread Bachsau
Change by Bachsau : -- title: `del OSError().characters_written` raises SystemError -> `del OSError().characters_written` raises `SystemError` ___ Python tracker <https://bugs.python.org/issu

[issue35504] `del OSError().characters_written` raises SystemError

2018-12-14 Thread Bachsau
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