➜

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 Scholes.C, christopher.hogan, hniksic, jbradaric, mark.dickinson, r.david.murray
Date 2015-08-11.19:04:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1439319846.65.0.443855085337.issue21167@psf.upfronthosting.co.za>
In-reply-to
Content 
Looks fine to me.  IIRC, we moved the PyFloat_FromString implementation away from using Py_NAN in Python 3 for exactly this reason.

On this point, though:

> An aggressively optimizing compiler could treat 0 * x = 0 no matter what x is.

Wouldn't such a compiler be in violation of the C standard, at least if it defines __STDC_IEC_559__?
History
Date User Action Args
2015-08-11 19:04:06mark.dickinsonsetrecipients: + mark.dickinson, hniksic, r.david.murray, jbradaric, Scholes.C, christopher.hogan
2015-08-11 19:04:06mark.dickinsonsetmessageid: <1439319846.65.0.443855085337.issue21167@psf.upfronthosting.co.za>
2015-08-11 19:04:06mark.dickinsonlinkissue21167 messages
2015-08-11 19:04:06mark.dickinsoncreate