This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients mark.dickinson, rhettinger, sree314
Date 2020-10-30.22:26:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1604096762.84.0.988224872115.issue42210@roundup.psfhosted.org>
In-reply-to
Content
Having fromhex() support signed NaNs was reasonable because it is a valid possible input; however, the case isn't as clear-cut for output. Since applications are allowed to ignore the sign bit, no application should rely on seeing a particular sign for a NaN.  

Also, existing applications may already have NaNs where the sign bit is set.  If we change the output, we could break their published examples and doctests.  So, this proposal may cause more harm than good.
History
Date User Action Args
2020-10-30 22:26:02rhettingersetrecipients: + rhettinger, mark.dickinson, sree314
2020-10-30 22:26:02rhettingersetmessageid: <1604096762.84.0.988224872115.issue42210@roundup.psfhosted.org>
2020-10-30 22:26:02rhettingerlinkissue42210 messages
2020-10-30 22:26:02rhettingercreate