[issue2900] math.copysign(1, float('nan'))

Mark Dickinson <[EMAIL PROTECTED]> added the comment: Closing this; I'm 99.72% sure the current behaviour is okay. :-) Christian, please feel free to reopen if you think further discussion is needed. -- resolution: -> invalid status: open -> closed __

[issue2900] math.copysign(1, float('nan'))

Mark Dickinson <[EMAIL PROTECTED]> added the comment: This is fine. copysign isn't supposed to propagate NaNs---it's just supposed to silently transfer the sign bit from the second argument to the first. So I think this is correct behaviour. Incidentally, on OS X: >>> from math import copys

[issue2900] math.copysign(1, float('nan'))

New submission from Christian Heimes <[EMAIL PROTECTED]>: What's your opinion on the edge case >>> math.copysign(1, float('nan')) 1.0 Is 1.0 the correct answer? IMHO Nan would be better ... -- assignee: marketdickinson components: Extension Modules messages: 66997 nosy: christian.heime