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 rhettinger
Recipients ChrisBarker, ezio.melotti, mark.dickinson, michael.foord, r.david.murray, rbcollins, rhettinger
Date 2016-06-04.03:10:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465009839.89.0.914867945875.issue27198@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW, I find assertClose easy to misinterpret.  At first, it looks like an assertion that a file is closed.  And once you mentally pronounce it like "close something that is open", it is harder to make the jump to "close as in nearby".

Also, I feed there is very little need for this. that we don't need another way to do it, and that the menagerie of specific asserts is getting harder to learn and remember (i.e. is easier to make up new assert methods than it is to remember what someone else wanted to name it).
History
Date User Action Args
2016-06-04 03:10:39rhettingersetrecipients: + rhettinger, mark.dickinson, rbcollins, ezio.melotti, r.david.murray, michael.foord, ChrisBarker
2016-06-04 03:10:39rhettingersetmessageid: <1465009839.89.0.914867945875.issue27198@psf.upfronthosting.co.za>
2016-06-04 03:10:39rhettingerlinkissue27198 messages
2016-06-04 03:10:39rhettingercreate