Stefan Krah <stefan-use...@bytereef.org> added the comment:
Mark Dickinson <rep...@bugs.python.org> wrote:
> I don't *think* this is related to issue 7281. I thought we'd determined that
> that issue
> had nothing to do with copysign itself, and everything to do with what the
> signbit of the
> NaN returned by float("nan") happens to be.
Yes, that's right. Also, to avoid spreading misinformation: The copysign(1.0,
float("nan"))
behavior is actually the same after changing float_repr_style.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue9069>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
