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 dingo, giampaolo.rodola, loewis, mark.dickinson
Date 2008-12-20.19:11:44
SpamBayes Score 4.8422e-11
Marked as misclassified No
Message-id <>
> Why do you say the return type is incorrect? It should, and does, 
> return a float.

The documentation at:

says, of round(x[, n]):

"""The return value is an integer if called with one argument, otherwise 
of the same type as x."""

On the other hand, PEP 3141 (which I didn't check before) seems to say 
that you're right: the return value should be an instance of Real.

So maybe this is just a doc bug?

I have to admit that I don't understand the motivation for round(int, n) 
returning a float, given that the value will always be integral.  It seems 
that this makes the two-argument version of round less useful to someone 
who's trying to avoid floats, perhaps working with ints and Decimals, or 
ints and Rationals, or just implementing fixed-point arithmetic with 
scaled ints.

But given that a behaviour change would be backwards incompatible, and the 
current behaviour is supported by at least one documentation source, it 
seems easiest to call this a doc bug.
Date User Action Args
2008-12-20 19:11:45mark.dickinsonsetrecipients: + mark.dickinson, loewis, giampaolo.rodola, dingo
2008-12-20 19:11:45mark.dickinsonsetmessageid: <>
2008-12-20 19:11:45mark.dickinsonlinkissue4707 messages
2008-12-20 19:11:44mark.dickinsoncreate