[issue28955] Not matched behavior of numeric comparison with the documentation

miss-islington added the comment: New changeset ca2fa2841f8e3ce5213a0e8c0abc1d0fdc7d386b by Miss Islington (bot) in branch '3.7': closes bpo-28955: Clarified comparisons between NaN and number in reference documentation (GH-5982)

[issue28955] Not matched behavior of numeric comparison with the documentation

Benjamin Peterson added the comment: New changeset ad8a0004206ba7aec5a8a60fce413da718080db2 by Benjamin Peterson (Tony Flury) in branch 'master': closes bpo-28955: Clarified comparisons between NaN and number in reference documentation (GH-5982)

[issue28955] Not matched behavior of numeric comparison with the documentation

Change by miss-islington : -- pull_requests: +8740 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28955] Not matched behavior of numeric comparison with the documentation

Change by Serhiy Storchaka : -- nosy: +mark.dickinson ___ Python tracker ___

[issue28955] Not matched behavior of numeric comparison with the documentation

Change by Anthony Flury : -- keywords: +patch pull_requests: +5748 stage: needs patch -> patch review ___ Python tracker

[issue28955] Not matched behavior of numeric comparison with the documentation

Change by Cheryl Sabella : -- keywords: +easy stage: -> needs patch type: behavior -> enhancement versions: +Python 3.7, Python 3.8 -Python 3.5 ___ Python tracker

[issue28955] Not matched behavior of numeric comparison with the documentation

R. David Murray added the comment: Sure, we like to make the docs more precise when it doesn't interfere with the presentation. Perhaps something like: "Additionally, ordering comparisions involving not-a-number values will always return False." I wonder if we should also mention here that

[issue28955] Not matched behavior of numeric comparison with the documentation

woo yoo added the comment: Maybe the description should be changed into "all order comparisons of not-a-number and any number will return False" -- ___ Python tracker

[issue28955] Not matched behavior of numeric comparison with the documentation

New submission from woo yoo: According to the documentation, which said "Additionally, comparing any number to a not-a-number value will return False. ",the comparison of `float('nan')!= 1`should yield False, while the result is True. Small errors like this in documentation should be