Antoine Pitrou added the comment: > > In any case, notifying people so they can quickly check their code > > seems much nicer than having them figure this out the hard way. > > I see it as a double-edged sword: if we start adding a warning for this > macro, people will expect us to do it for every other macro, which we > aren't doing right now.
And also, as this issue shows, we may have to change it in a bugfix release, which means people shouldn't trust the fact that there's no such warning, anyway. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue16602> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
