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 vstinner
Recipients LambertDW, ajaksu2, dingo, giampaolo.rodola, gvanrossum, jyasskin, loewis, mark.dickinson, orsenthil, rhettinger, vstinner
Date 2009-01-28.09:35:45
SpamBayes Score 7.570679e-06
Marked as misclassified No
Message-id <1233135347.76.0.623056739692.issue4707@psf.upfronthosting.co.za>
In-reply-to
Content
marketdickinson> (2) Accuracy

I see int/float like bytes/characters: it's not a good idea to mix 
them. If you use float, you know that you loose precision (digits) 
after some operations. Whereas I suppose the operations on int are 
always exact.

I like round(int,int)->int (same input/output types). To get a float, 
use round(float(int), int)->float.
History
Date User Action Args
2009-01-28 09:35:48vstinnersetrecipients: + vstinner, gvanrossum, loewis, rhettinger, mark.dickinson, orsenthil, giampaolo.rodola, ajaksu2, jyasskin, LambertDW, dingo
2009-01-28 09:35:47vstinnersetmessageid: <1233135347.76.0.623056739692.issue4707@psf.upfronthosting.co.za>
2009-01-28 09:35:45vstinnerlinkissue4707 messages
2009-01-28 09:35:45vstinnercreate