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 mark.dickinson, pitrou, steve.dower, tim.golden, zach.ware
Date 2014-10-09.19:43:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412883836.74.0.191350697903.issue22590@psf.upfronthosting.co.za>
In-reply-to
Content
More info: the reason for the difference is that in Python 3.4, float("nan") and float("inf") create the float directly from the appropriate bit-pattern, rather than deferring to the platform's definition of nan.  This change was introduced to avoid obscure problems on platforms where the Py_NAN macros were causing compile-time errors.  There should be a (resolved, fixed) issue about this somewhere on the tracker, but I don't have the number handy right now.

I don't consider this a bug.
History
Date User Action Args
2014-10-09 19:43:56mark.dickinsonsetrecipients: + mark.dickinson, pitrou, tim.golden, zach.ware, steve.dower
2014-10-09 19:43:56mark.dickinsonsetmessageid: <1412883836.74.0.191350697903.issue22590@psf.upfronthosting.co.za>
2014-10-09 19:43:56mark.dickinsonlinkissue22590 messages
2014-10-09 19:43:56mark.dickinsoncreate