[issue8704] cgitb sends a bogus HTTP header if the app crashes before finishing headers
coyot linden added the comment: Ran into this also, got: AH02429: Response header name '
[issue35077] Make TypeError message less ambiguous
coyot linden added the comment: 3.8 has come and gone, resubmitting this for 3.10 -- versions: +Python 3.10 -Python 3.8 ___ Python tracker <https://bugs.python.org/issue35077> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35077] Make TypeError message less ambiguous
New submission from coyot linden : The TypeError message: TypeError: string indices must be integers is ambiguously written. While some may understand the intent, others will read it as confusingly saying that strings must be integers since dicts among other things do have string indices. Suggest changing the message to: TypeError: indices of strings must be integers -- messages: 328565 nosy: coyot priority: normal severity: normal status: open title: Make TypeError message less ambiguous type: enhancement versions: Python 3.5 ___ Python tracker <https://bugs.python.org/issue35077> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35077] Make TypeError message less ambiguous
coyot linden added the comment: You're welcome. I filed against 3.5 because that's what I have in our env at the moment and I couldn't test and thus assert the issue in later versions. Happy to see the problem addressed more generally. The abstraction of the problem is the ambiguity in English between nouns used as adjectives and their groupings: (noun phrase) versus (noun as adjective)(noun). Using "X of Y" rather than (XY) or (X)(Y) resolves the ambiguity. -- ___ Python tracker <https://bugs.python.org/issue35077> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35077] Make TypeError message less ambiguous
coyot linden added the comment: The problem I have with "So only the 'index of string' interpretation makes sense." is that by the time a developer has that understanding, they won't get this error. So it's fine and logical to say from the behind-the-scenes view that only sequences talk about indices, but that's not helpful to the confused developer who gets this message. The point of error messages should be to clearly indicate the problem and solution, not rely on the developer having a global understanding of error messages. So, rather than defend the current practice, I ask if there are arguments against "X of Y". Is there some context in which that is confusing? -- ___ Python tracker <https://bugs.python.org/issue35077> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue35077] Make TypeError message less ambiguous
coyot linden added the comment: Sure, this can wait to the next release. I don't see it as groundshatteringly ;) urgent. -- ___ Python tracker <https://bugs.python.org/issue35077> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
