| commit | 51e2651b298cf59653133baf556f4cca3c569583 | [log] [tgz] |
|---|---|---|
| author | Tim Peters <tim.peters@gmail.com> | Fri Sep 07 08:45:55 2001 +0000 |
| committer | Tim Peters <tim.peters@gmail.com> | Fri Sep 07 08:45:55 2001 +0000 |
| tree | c2e498784340f340ce0809b2df18237955dca40a | |
| parent | 9652de9d825f2e377c4238145cc914bd28fa7111 [diff] |
SF bug [#458941] Looks like a unary minus bug. com_factor(): when a unary minus is attached to a float or imaginary zero, don't optimize the UNARY_MINUS opcode away: the const dict can't distinguish between +0.0 and -0.0, so ended up treating both like the first one added to it. Optimizing UNARY_PLUS away isn't a problem. (BTW, I already uploaded the 2.2a3 Windows installer, and this isn't important enough to delay the release.)