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 mark.dickinson
Recipients ethan.furman, mark.dickinson, vstinner
Date 2015-01-07.18:18:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420654688.28.0.20149240599.issue23185@psf.upfronthosting.co.za>
In-reply-to
Content
> Why does Python return the same representation for positive and negative NaN?

History, perhaps?  In any case, the sign of a NaN isn't useful information in the same way that the sign of an infinity is.  The IEEE 754 standard explicitly refuses to attach any meaning to the sign bit of a NaN.  And if we were aiming for a full and faithful representation of NaNs, we'd want to output the payload, too (which is just about as meaningless / meaningful as the sign bit).
History
Date User Action Args
2015-01-07 18:18:08mark.dickinsonsetrecipients: + mark.dickinson, vstinner, ethan.furman
2015-01-07 18:18:08mark.dickinsonsetmessageid: <1420654688.28.0.20149240599.issue23185@psf.upfronthosting.co.za>
2015-01-07 18:18:08mark.dickinsonlinkissue23185 messages
2015-01-07 18:18:08mark.dickinsoncreate