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 Tomáš Petříček
Recipients Tomáš Petříček
Date 2017-11-15.23:31:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510788720.0.0.213398074469.issue32042@psf.upfronthosting.co.za>
In-reply-to
Content
This option can be seen as a more general case of the options already available which lift the requirement of exact representation match (True for 1, normalize whitespace etc.). It would enable easier testing of relevant behavior instead of repr's artifacts.

An implementation draft is at https://github.com/tpet/cpython/commit/e59cc2d2c854f5995c36a60410eca0e893a7e269

As the expected value has to be reconstructed from the string representation anyway, it seems reasonable to do that for both values (expected and got). Only minor modifications seem to be required in that case.
History
Date User Action Args
2017-11-15 23:32:00Tomáš Petříčeksetrecipients: + Tomáš Petříček
2017-11-15 23:32:00Tomáš Petříčeksetmessageid: <1510788720.0.0.213398074469.issue32042@psf.upfronthosting.co.za>
2017-11-15 23:31:59Tomáš Petříčeklinkissue32042 messages
2017-11-15 23:31:59Tomáš Petříčekcreate