[Python-Dev] operator precedence of eq, ne, etc, if both object have implementations (original) (raw)
Chris Withers chris at simplistix.co.uk
Wed Sep 30 16:24:32 CEST 2009
- Previous message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
- Next message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
+1, and supported by documentation.
Something like a manuel-based table test would seem ideal for this:
http://packages.python.org/manuel/manuel/table-example.html
..but what are the chances of something like that getting into the python core docs?
Chris
-- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
- Previous message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
- Next message: [Python-Dev] operator precedence of __eq__, __ne__, etc, if both object have implementations
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]