This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author abarry
Recipients abarry, ezio.melotti, gvanrossum, martin.panter, r.david.murray, serhiy.storchaka, vstinner, ztane
Date 2016-06-27.11:30:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467027010.6.0.830111884742.issue27364@psf.upfronthosting.co.za>
In-reply-to
Content
I think ultimately a SyntaxError should be fine. I don't know *when* it becomes appropriate to change a warning into an error; I was thinking 3.7 but, as Serhiy said, there's no rush. I think waiting five release cycles is overkill though, that means the error won't be until 8 years from now (assuming release cycle periods don't change)! I think at most 3.8 should be fine for making this a full-on syntax error.
History
Date User Action Args
2016-06-27 11:30:10abarrysetrecipients: + abarry, gvanrossum, vstinner, ezio.melotti, r.david.murray, martin.panter, serhiy.storchaka, ztane
2016-06-27 11:30:10abarrysetmessageid: <1467027010.6.0.830111884742.issue27364@psf.upfronthosting.co.za>
2016-06-27 11:30:10abarrylinkissue27364 messages
2016-06-27 11:30:10abarrycreate