[IronPython] Issue Triage

Dino Viehland dinov at microsoft.com
Mon Jan 17 05:07:21 CET 2011

My general attitude has been that CPython is always more correct, even when it's not.  :)  We usually have our own tests for things like this (which we run against CPython too) and when CPython fixes it we'll fix it too.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Brian Curtin
Sent: Sunday, January 16, 2011 3:13 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Issue Triage

On Sun, Jan 16, 2011 at 16:06, Richard Nienaber <rjnienaber at gmail.com<mailto:rjnienaber at gmail.com>> wrote:
Having said that, I'm still looking for a guideline about what to do in the scenario where the behaviour of IronPython is more 'correct' than CPython.


I would suggest creating issues on the CPython bug tracker for those cases, and feel free to add me to the nosy list of any of them (tracker ID: brian.curtin).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20110117/ff4459f1/attachment.html>

More information about the Ironpython-users mailing list