Mark Dickinson dickinsm at gmail.com
Wed Sep 23 13:06:09 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 ]

---

On Wed, Sep 23, 2009 at 4:43 AM,  <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

Mark

---

• 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 ]

---

More information about the Python-Dev mailing list