Emanuel Barry added the comment: 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).
---------- assignee: ebarry -> _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue28128> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com