➜

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 tim.peters
Recipients drj, eric.smith, mark.dickinson, tim.peters
Date 2009-06-30.14:16:41
SpamBayes Score 0.000511245
Marked as misclassified No
Message-id <1246371404.11.0.18336994862.issue6387@psf.upfronthosting.co.za>
In-reply-to
Content 
Yup, -1 here too.  For dyadic arithmetic operations (+ - * / % //) on
mixed numeric types, Python's execution model coerces the operands to a
common type before computation begins.  Besides just being the way it's
worked "forever" in Python, it's consistent and explainable.  Growing a
wart for one case of one case would be inconsistent and deeply
surprising at a higher level.  Live with it ;-)
History
Date User Action Args
2009-06-30 14:16:44tim.peterssetrecipients: + tim.peters, mark.dickinson, eric.smith, drj
2009-06-30 14:16:44tim.peterssetmessageid: <1246371404.11.0.18336994862.issue6387@psf.upfronthosting.co.za>
2009-06-30 14:16:42tim.peterslinkissue6387 messages
2009-06-30 14:16:42tim.peterscreate