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 cjw296
Recipients Eli Rose, asfaltboy, cjw296, mariocj89, michael.foord, rhettinger, xtreak
Date 2018-12-11.06:33:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544509995.56.0.788709270274.issue28054@psf.upfronthosting.co.za>
In-reply-to
Content
This is a tricky one as there's plenty of prior art, with pytest's assertion rewriting [1], testfixtures compare [2] and the stuff that unittest already does [3].

I don't think any solution should rely on a TestCase being used as pytest, which is the most prevalent testing framework now, doesn't want to rely on them (they do come with a lot of baggage ;-)).

Can we make use of the pretty diffing stuff in unittest without explicitly making it a requirement?

[1] https://docs.pytest.org/en/latest/assert.html

[2] https://testfixtures.readthedocs.io/en/latest/comparing.html#dicts

[3] https://docs.python.org/3.8/library/unittest.html#unittest.TestCase.assertDictEqual
History
Date User Action Args
2018-12-11 06:33:15cjw296setrecipients: + cjw296, rhettinger, michael.foord, asfaltboy, Eli Rose, mariocj89, xtreak
2018-12-11 06:33:15cjw296setmessageid: <1544509995.56.0.788709270274.issue28054@psf.upfronthosting.co.za>
2018-12-11 06:33:15cjw296linkissue28054 messages
2018-12-11 06:33:15cjw296create