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 michael.foord
Recipients Max Rothman, michael.foord, rhettinger
Date 2017-07-11.19:04:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499799891.86.0.476722409403.issue30821@psf.upfronthosting.co.za>
In-reply-to
Content
Generally the called with asserts can only be used to match the *actual call*, and they don't determine "equivalence". 

To do it cleanly would be tricky, and adding complex code is a maintenance burden. I'm not convinced there's a massive use case - generally you want to make asserts about what your code actually does - not just check if it does something equivalent to your assert.

So I'm not enthusiastic about this.
History
Date User Action Args
2017-07-11 19:04:51michael.foordsetrecipients: + michael.foord, rhettinger, Max Rothman
2017-07-11 19:04:51michael.foordsetmessageid: <1499799891.86.0.476722409403.issue30821@psf.upfronthosting.co.za>
2017-07-11 19:04:51michael.foordlinkissue30821 messages
2017-07-11 19:04:51michael.foordcreate