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 gvanrossum
Recipients abarry, ezio.melotti, gvanrossum, martin.panter, r.david.murray, serhiy.storchaka, vstinner, ztane
Date 2016-06-27.15:00:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
I think ultimately it has to become an error (otherwise I wouldn't
have agreed to the warning, silent or not). But because there's so
much 3rd party code that depends on it we indeed need to take
"several" releases before we go there.

Contacting the PyCQA folks would also be a great idea -- can anyone
volunteer to do so?
Date User Action Args
2016-06-27 15:00:28gvanrossumsetrecipients: + gvanrossum, vstinner, ezio.melotti, r.david.murray, martin.panter, serhiy.storchaka, ztane, abarry
2016-06-27 15:00:28gvanrossumlinkissue27364 messages
2016-06-27 15:00:27gvanrossumcreate