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 ahrvoje, eric.smith, mark.dickinson
Date 2016-04-19.06:20:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461046812.58.0.216068172964.issue26785@psf.upfronthosting.co.za>
In-reply-to
Content
The sign of a NaN *is* fully supported, and easily accessible to those who need it. It just isn't part of the repr. Given that the sign is meaningless in the vast majority of applications, I think Python does the right thing here by leaving it out of the repr, rather than cluttering up the repr with meaningless and potentially confusing information.

I'll leave the last word to Stephen Canon, from the SO answer I linked to above:

" it is almost always a bug to attach meaning to the "sign bit" of a NaN datum."
History
Date User Action Args
2016-04-19 06:20:12mark.dickinsonsetrecipients: + mark.dickinson, eric.smith, ahrvoje
2016-04-19 06:20:12mark.dickinsonsetmessageid: <1461046812.58.0.216068172964.issue26785@psf.upfronthosting.co.za>
2016-04-19 06:20:12mark.dickinsonlinkissue26785 messages
2016-04-19 06:20:12mark.dickinsoncreate