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-boun...@lists.ironpython.com [mailto:users-boun...@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 <rjniena...@gmail.com<mailto:rjniena...@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. Richard 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).
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
