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>
Python-bugs-list mailing list

Reply via email to