[Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
eric at trueblade.com
Wed Sep 23 15:01:52 CEST 2009
skip at pobox.com wrote:
> Dino> For IronPython we wrote a set of tests which go through and define
> Dino> the various operator methods in all sorts of combinations on both
> Dino> new-style and old-style classes as well as subclasses of those
> Dino> classes and then do the comparisons w/ logging.
> It would be very nice if these complex corner cases had a set of test
> cases which could be run by all implementations (CPython, Jython,
> IronPython, PyPy, etc). I don't know. Maybe the CPython test suite serves
> that purpose, but it seems like it would be helpful if this sort of
> "validation suite" was maintained as a separate project all implementations
> could use and contribute to.
IIRC, one of the reasons for "breaking out" the standard library (and
its test suite) was to allow for things like this.
 For whatever definition "breaking out" ends up having.
More information about the Python-Dev