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 christian.heimes, mark.dickinson
Date 2008-06-24.10:47:32
SpamBayes Score 0.0012068895
Marked as misclassified No
Message-id <1214304455.81.0.663476079399.issue3188@psf.upfronthosting.co.za>
In-reply-to
Content
2.6 adds float('inf') and float('nan') as cross-platform ways to 
generate infinities and NaNs.  The C99 standard (section 7.20.1.3, 
paragraph 3) specifies that 'infinity' (in any case, with optional 
preceding sign) should also be a valid input to strtod, and I propose 
that in Python float('infinity') should correspondingly be valid.

Note that the IEEE 754 standard also states that 'inf' and 'infinity' 
should be valid input string representations of infinity, and Python's 
decimal module also allows both 'inf' and 'infinity'.

A patch is attached.

Unless I'm mistaken, this change is simple and unlikely to be 
controversial.  I plan to check it in in a week or two if there's no 
feedback before then.
History
Date User Action Args
2008-06-24 10:47:36mark.dickinsonsetspambayes_score: 0.00120689 -> 0.0012068895
recipients: + mark.dickinson, christian.heimes
2008-06-24 10:47:35mark.dickinsonsetspambayes_score: 0.00120689 -> 0.00120689
messageid: <1214304455.81.0.663476079399.issue3188@psf.upfronthosting.co.za>
2008-06-24 10:47:34mark.dickinsonlinkissue3188 messages
2008-06-24 10:47:33mark.dickinsoncreate