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 facundobatista
Recipients facundobatista, gvanrossum, mark.dickinson, rhettinger
Date 2008-01-10.12:09:44
SpamBayes Score 0.025345879
Marked as misclassified No
Message-id <1199966988.34.0.585415323525.issue1780@psf.upfronthosting.co.za>
In-reply-to
Content
I think that the Spec disallows additional whitespace to not allow, for
example, "2. 34" as "2.34", or "10 e-12".

I don't see any harm in having "  2.34" or "5.73\n" as good input
values, as long we remove those characters at both ends.

I propose to just make a .strip() at the input string, change the
documentation to reflect this, and that's all.

The doc says: "If value is a string, it should conform to the decimal
numeric string syntax:"

We can put: "If value is a string, it should conform to the decimal
numeric string syntax after being stripped on both ends:"
History
Date User Action Args
2008-01-10 12:09:48facundobatistasetspambayes_score: 0.0253459 -> 0.025345879
recipients: + facundobatista, gvanrossum, rhettinger, mark.dickinson
2008-01-10 12:09:48facundobatistasetspambayes_score: 0.0253459 -> 0.0253459
messageid: <1199966988.34.0.585415323525.issue1780@psf.upfronthosting.co.za>
2008-01-10 12:09:46facundobatistalinkissue1780 messages
2008-01-10 12:09:45facundobatistacreate