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, skrah, steven.daprano
Date 2012-08-03.12:26:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1343996793.31.0.751630257687.issue15544@psf.upfronthosting.co.za>
In-reply-to
Content
> IEEE 754 doesn't help here, since it doesn't cover decimal
> floating-point <-> binary floating-point conversions.

OTOH, IEEE 754 *does* cover floating-point to int conversions (5.4.1, 5.8):  those fall under 'general-computational operations', and as such should signal when given an sNaN (6.2: "Signaling NaNs shall be reserved operands that, under default exception handling, signal the invalid operation exception (see 7.2) for every general-computational and signaling-computational operation except for the conversions described in 5.12. For non-default treatment, see 8.").  It feels to me as though decimal -> binary conversions should follow the same pattern.
History
Date User Action Args
2012-08-03 12:26:33mark.dickinsonsetrecipients: + mark.dickinson, steven.daprano, skrah
2012-08-03 12:26:33mark.dickinsonsetmessageid: <1343996793.31.0.751630257687.issue15544@psf.upfronthosting.co.za>
2012-08-03 12:26:32mark.dickinsonlinkissue15544 messages
2012-08-03 12:26:32mark.dickinsoncreate