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, r.david.murray, terry.reedy, umedoblock
Date 2011-06-04.14:43:28
SpamBayes Score 2.105555e-08
Marked as misclassified No
Message-id <1307198609.04.0.0162109872269.issue12211@psf.upfronthosting.co.za>
In-reply-to
Content
How about something like: "Return a float with the magnitude of x but the sign of y."?

The behaviour of math.copysign with respect to non-float inputs matches that of almost all the other math module functions:  integer arguments are first converted to floats, and then the underlying libm function applied.  I'm not convinced that changing the behaviour of copysign to produce integer results for integer argument would be a good idea.
History
Date User Action Args
2011-06-04 14:43:29mark.dickinsonsetrecipients: + mark.dickinson, terry.reedy, r.david.murray, umedoblock
2011-06-04 14:43:29mark.dickinsonsetmessageid: <1307198609.04.0.0162109872269.issue12211@psf.upfronthosting.co.za>
2011-06-04 14:43:28mark.dickinsonlinkissue12211 messages
2011-06-04 14:43:28mark.dickinsoncreate