Author BCSharp
Recipients Anthony Sottile, BCSharp, SilentGhost, benjamin.peterson, brett.cannon, gvanrossum, yselivanov
Date 2019-05-20.20:27:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558384040.78.0.286073728056.issue36919@roundup.psfhosted.org>
In-reply-to
Content
> I'm assuming the real issue is wanting to make IronPython pass as much of the CPython test suite as possible.

This is indeed the case. The CPython test suite is invaluable in guiding IronPython development. Most of the time, the tests are pretty good to gloss over implementation artifacts (usually error messages), so that they work for IronPython as well, despite some differences between CPython and IronPython.

There are a few cases, however, when the tests expect behavior that is implementation-specific and difficult to match in IronPython, or is proper Python but impossible to match for IronPython. For all such cases I would like to submit patches to the CPython repo, but I am new to this process. Should such case first be reported on bpo, python-dev, or just straight a github PR?

Sometimes, by writing additional tests for IronPython we discover what seems as possible bugs in CPython. I was planning to submit reports for them on bpo, assuming this is the proper place to discuss them, but perhaps python-dev is a better place.

> So fixing the tests to allow it either way sounds good.

A github PR is on its way.
History
Date User Action Args
2019-05-20 20:27:20BCSharpsetrecipients: + BCSharp, gvanrossum, brett.cannon, benjamin.peterson, SilentGhost, yselivanov, Anthony Sottile
2019-05-20 20:27:20BCSharpsetmessageid: <1558384040.78.0.286073728056.issue36919@roundup.psfhosted.org>
2019-05-20 20:27:20BCSharplinkissue36919 messages
2019-05-20 20:27:20BCSharpcreate