Gregory P. Smith added the comment:
When we added this functionality to assertEqual we were *intentionally*
conservative on when it would auto-promote to nicer equality comparison
functions. It needs to behave exactly as == would in all situations.
(1,2,3) == [1,2,3]
False
We must maintain
R. David Murray added the comment:
That sounds like a bug.
--
title: assertSequenceEqual should be fired when comparing sequences -
assertSequenceEqual should be fired when comparing sequence subclasses
___
Python tracker rep...@bugs.python.org
Ezio Melotti added the comment:
The assertSequenceEqual docs[0] say:
This method is not called directly by assertEqual(), but it’s used to implement
assertListEqual() and assertTupleEqual().
The asserEqual docs[1] say:
In addition, if first and second are the exact same type and one of
