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, martin.panter, ned.deily, r.david.murray, serhiy.storchaka, yan12125
Date 2016-09-15.10:51:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473936700.35.0.493647124651.issue28128@psf.upfronthosting.co.za>
In-reply-to
Content
Besides converting the DeprecationWarning to a Syntax{Error,Warning}, I don't see an easy way to include the offending line (or even file). The place in the code where the strings are created has no idea *where* they are being defined. AIUI, either we special-case this, or we resolve #28028 (but I don't think the latter can go in 3.6).
History
Date User Action Args
2016-09-15 10:51:40abarrysetrecipients: + abarry, ned.deily, r.david.murray, martin.panter, serhiy.storchaka, yan12125
2016-09-15 10:51:40abarrysetmessageid: <1473936700.35.0.493647124651.issue28128@psf.upfronthosting.co.za>
2016-09-15 10:51:40abarrylinkissue28128 messages
2016-09-15 10:51:40abarrycreate