➜

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 belopolsky
Recipients alex, belopolsky, daniel.urban, mark.dickinson, rhettinger
Date 2011-05-21.19:58:02
SpamBayes Score 3.873047e-10
Marked as misclassified No
Message-id <BANLkTima8LB175Ztonn1PR3kKPjj1MjLvw@mail.gmail.com>
In-reply-to <1306007448.52.0.148624714861.issue11949@psf.upfronthosting.co.za>
Content 
On Sat, May 21, 2011 at 3:50 PM, Mark Dickinson <report@bugs.python.org> wrote:
..
> On the idea of a warning, I don't really see the point;  I find it hard to imagine it's really going to catch many real errors.

My experience is different.  In my work, NaNs often creep into
calculations that are not designed to deal with them. (More often from
data files than from invalid operations.)  Sorting a large list with a
handful of NaNs, often leads to rather mysterious errors if not to
silently wrong results.  I believe there was even an issue on the
tracker about this particular case.
History
Date User Action Args
2011-05-21 19:58:03belopolskysetrecipients: + belopolsky, rhettinger, mark.dickinson, alex, daniel.urban
2011-05-21 19:58:02belopolskylinkissue11949 messages
2011-05-21 19:58:02belopolskycreate