[issue40177] Python Language Reference Documentation

New submission from Arnuld : In section "6.10.1 Value comparisons", it is written: https://docs.python.org/3/reference/expressions.html "The not-a-number values float('NaN') and decimal.Decimal('NaN') are special. Any ordered comparison of a number to a not-a-number value is false. A counter-in

[issue40177] Python Language Reference Documentation

Change by Karthikeyan Singaravelan : -- nosy: +mark.dickinson, rhettinger, stutzbach ___ Python tracker ___ ___ Python-bugs-list mai

[issue40176] unterminated string literal tokenization error messages could be better

Alex Gaynor added the comment: Here's my suggestion: End of line reached without finding the end of string literal. Are you missing a closing quote? -- nosy: +alex ___ Python tracker __

[issue40120] Undefined C behavior going beyond end of struct via a [1] arrays.

Gregory P. Smith added the comment: agreed, being opaque seems ideal. -- ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue40120] Undefined C behavior going beyond end of struct via a [1] arrays.

Gregory P. Smith added the comment: PyBytesObject could become a struct that contains a single opaque internal struct. there is some code out there that references PyBytesObjects internals by field name but my searches across a broad swath of code so far seem to suggest that is so rare this

[issue40177] Python Language Reference Documentation

Steven D'Aprano added the comment: How about this? "The not-a-number values ``float('NaN')`` and ``decimal.Decimal('NaN')`` are special. Not-a-number values always compare unordered and unequal to any other value, including themselves. For example, if ``x = float('NaN')``, then ``x == x``,

[issue40177] Python Language Reference Documentation

Steven D'Aprano added the comment: Oops, that should be ... ``x == x``, ``3 < x``, and ``x > 3`` are all false ... -- ___ Python tracker ___ _

[issue40177] Python Language Reference Documentation

Steven D'Aprano added the comment: Oh never mind, I'm just going to slink away now and stop posting corrections when distracted... -- ___ Python tracker ___ _

[issue40176] unterminated string literal tokenization error messages could be better

Ammar Askar added the comment: Just re-posting this here from the open PR. Rust's handling of this seems nice and beginner friendly: error: unterminated double quote string --> src/main.rs:2:19 | 2 | let message = "Hello world | ___^ 3 | | println!(

[issue40126] Incorrect error handling in unittest.mock

Change by Karthikeyan Singaravelan : -- nosy: +cjw296, xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

<    1   2