Message342947
| Author | gvanrossum |
|---|---|
| Recipients | Anthony Sottile, BCSharp, SilentGhost, benjamin.peterson, brett.cannon, gvanrossum, yselivanov |
| Date | 2019-05-20.19:45:58 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1558381558.38.0.905969494253.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. I am okay with interpretation (B) in this case -- I can totally see that other parsing strategies have no use for adding the '\n' character to the end of the string. But I don't want to declare that CPython is wrong to show the '\n' -- it seems a pretty harmless artifact. So fixing the tests to allow it either way sounds good. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-05-20 19:45:58 | gvanrossum | set | recipients: + gvanrossum, brett.cannon, benjamin.peterson, SilentGhost, yselivanov, Anthony Sottile, BCSharp |
| 2019-05-20 19:45:58 | gvanrossum | set | messageid: <1558381558.38.0.905969494253.issue36919@roundup.psfhosted.org> |
| 2019-05-20 19:45:58 | gvanrossum | link | issue36919 messages |
| 2019-05-20 19:45:58 | gvanrossum | create | |