- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message59152
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 | christian.heimes |
|---|---|
| Recipients | Rhamphoryncus, christian.heimes, gvanrossum, mark.dickinson |
| Date | 2008-01-03.20:21:15 |
| SpamBayes Score | 0.0949642 |
| Marked as misclassified | No |
| Message-id | <477D43B9.3000109@cheimes.de> |
| In-reply-to | <ca471dc20801030928w60159d74g4a04e45073aefcaa@mail.gmail.com> |
| Content | |
|---|---|
Guido van Rossum wrote: > Hm, OK, but then passing a zero of some other type (e.g. int) should > also return +1 as the sign. I also think the function's name should be > changed, because I (and I assume many others) have grown up with a > sign() function that essentially returns cmp(x, 0.0). > > Perhaps it would be better to have a function math.isneg() that > returns True for -0.0 and anything smaller and False for +0.0 and > anything larger. It could also return the proper sign of a nan. I'm fine with a isneg() function but I wouldn't "fix" it for NaN. It has probably some kind of obscure meaning. The best explanation I was able to find, is http://www.cisl.ucar.edu/docs/trap.error/errortypes.html "Note: Since NaN is "not a number," there really isn't a "+" or "-" sign associated with it." Christian |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008-01-03 20:21:15 | christian.heimes | set | spambayes_score: 0.0949642 -> 0.0949642 recipients: + christian.heimes, gvanrossum, mark.dickinson, Rhamphoryncus |
| 2008-01-03 20:21:15 | christian.heimes | link | issue1640 messages |
| 2008-01-03 20:21:15 | christian.heimes | create | |

