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 mark.dickinson, steven.daprano
Date 2016-09-06.17:24:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473182673.74.0.140845727903.issue27975@psf.upfronthosting.co.za>
In-reply-to
Content
I see this as a documentation issue: the vast majority of math module functions are designed to operate on floats, and if given a non-float input, simply convert that input to a float as a convenience. If we start special-casing math module functions for int, Fraction, and Decimal inputs, the module is going to become much more complicated both in terms of implementation and in terms of cognitive load for the user.
History
Date User Action Args
2016-09-06 17:24:33mark.dickinsonsetrecipients: + mark.dickinson, steven.daprano
2016-09-06 17:24:33mark.dickinsonsetmessageid: <1473182673.74.0.140845727903.issue27975@psf.upfronthosting.co.za>
2016-09-06 17:24:33mark.dickinsonlinkissue27975 messages
2016-09-06 17:24:33mark.dickinsoncreate