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 eric.smith, mark, mark.dickinson
Date 2008-05-09.14:23:25
SpamBayes Score 0.0001817011
Marked as misclassified No
Message-id <>
> I think that n should stay the same for floats, but for integers should
> never switch to g, but just use as many separators as needed.

I agree with this, in principle.  It might be some work to implement, 
though:  for floats, Python gets to use the OS-supplied formatting 
functions.  Indeed, it looks as though all that happens here is that the 
integer is converted to a float before formatting:

>>> print("{0:n} ".format(10**400), end="")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OverflowError: Python int too large to convert to C double

For integers, we'd have to roll our own code. I had similar problems 
trying to implement the 'n' format code for Decimal;  in the end I just 
gave up and left it unimplemented.  Maybe using 'n' for an integer should 
just raise an exception, for now?

Eric, what do you think?
Date User Action Args
2008-05-09 14:23:30mark.dickinsonsetspambayes_score: 0.000181701 -> 0.0001817011
recipients: + mark.dickinson, eric.smith, mark
2008-05-09 14:23:29mark.dickinsonsetspambayes_score: 0.000181701 -> 0.000181701
messageid: <>
2008-05-09 14:23:28mark.dickinsonlinkissue2802 messages
2008-05-09 14:23:26mark.dickinsoncreate