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 cdavid, cito, dino.viehland, eric.smith, mark.dickinson, stutzbach
Date 2009-04-22.22:46:07
SpamBayes Score 0.005259893
Marked as misclassified No
Message-id <1240440369.78.0.295171052783.issue4482@psf.upfronthosting.co.za>
In-reply-to
Content
> Maybe if you explicitly ask for the "sign" of a NaN, it should
> always be a space.

Actually, I think '+nan' for format(float('nan'), '+'), and ' nan'
for format(float('nan'), ' ').  Then nans and infs can be treated 
identically, except that the sign of a nan is always considered to be 
positive, regardless of what the _Py_dg_dtoa function returns.

> And when requesting leading zeros, you also get leading spaces
> instead?

Should do the same thing for nans and infs here.  But certainly leading 
zeros should be avoided.  Leading spaces sounds fine to me.
History
Date User Action Args
2009-04-22 22:46:09mark.dickinsonsetrecipients: + mark.dickinson, cito, eric.smith, stutzbach, cdavid, dino.viehland
2009-04-22 22:46:09mark.dickinsonsetmessageid: <1240440369.78.0.295171052783.issue4482@psf.upfronthosting.co.za>
2009-04-22 22:46:08mark.dickinsonlinkissue4482 messages
2009-04-22 22:46:07mark.dickinsoncreate