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 serhiy.storchaka
Recipients ezio.melotti, michael.foord, pitrou, rbcollins, serhiy.storchaka
Date 2017-05-01.17:49:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493660968.68.0.337870939231.issue30221@psf.upfronthosting.co.za>
In-reply-to
Content
This will save time and memory of unittest users for reading the documentation, remembering it and trying to understand in which cases assertNotAlmostEqual() can be used. This will prevent them from using unsuitable method.

I found only one case of using assertNotAlmostEqual() in the wild, and it doesn't look a proper use. Do you have any cases in which it is useful?

Recently I did have a discussion with Giampaolo about changes to assertAlmostEqual() and assertNotAlmostEqual() [1]. If assertNotAlmostEqual() didn't exist this discussion would even not started. So this would save my and Giampaolo's time.

[1] https://github.com/python/cpython/pull/1331
History
Date User Action Args
2017-05-01 17:49:28serhiy.storchakasetrecipients: + serhiy.storchaka, pitrou, rbcollins, ezio.melotti, michael.foord
2017-05-01 17:49:28serhiy.storchakasetmessageid: <1493660968.68.0.337870939231.issue30221@psf.upfronthosting.co.za>
2017-05-01 17:49:28serhiy.storchakalinkissue30221 messages
2017-05-01 17:49:28serhiy.storchakacreate