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 terry.reedy
Recipients docs@python, mark.dickinson, r.david.murray, sandro.tosi, terry.reedy, umedoblock
Date 2011-06-26.16:54:18
SpamBayes Score 1.9257386e-06
Marked as misclassified No
Message-id <1309107258.76.0.141486345153.issue12211@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with adding '(absolute value)'. I think the following covers the NaN behavior. "NaN acts as a positive value that cannot be negated." This should be added to both doc and docstring.

I do not think we generally specify the nan behavior for each function, but it usually follows general rules. The copysign(x,nan) behavior is not obvious as nan, like int 0, does not really have a sign. One might expect copysign(-1.0,nan) to be -1.
History
Date User Action Args
2011-06-26 16:54:18terry.reedysetrecipients: + terry.reedy, mark.dickinson, r.david.murray, sandro.tosi, docs@python, umedoblock
2011-06-26 16:54:18terry.reedysetmessageid: <1309107258.76.0.141486345153.issue12211@psf.upfronthosting.co.za>
2011-06-26 16:54:18terry.reedylinkissue12211 messages
2011-06-26 16:54:18terry.reedycreate