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 Nathan Herring, ezio.melotti, michael.foord, rbcollins, rhettinger
Date 2015-11-23.11:40:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448278848.92.0.789025622452.issue25669@psf.upfronthosting.co.za>
In-reply-to
Content
assertEqual *does* do type checking and it's strict that it will only resort to the "type specific" assert checks if both types are of the same type. In the general case it's impossible to know whether comparing a subclass with the type specific check is the right thing to do - so unittest doesn't guess.

As you have a simple workaround ( dict(foo) ) I'm closing this.
History
Date User Action Args
2015-11-23 11:40:49michael.foordsetrecipients: + michael.foord, rhettinger, rbcollins, ezio.melotti, Nathan Herring
2015-11-23 11:40:48michael.foordsetmessageid: <1448278848.92.0.789025622452.issue25669@psf.upfronthosting.co.za>
2015-11-23 11:40:48michael.foordlinkissue25669 messages
2015-11-23 11:40:48michael.foordcreate