Terry J. Reedy <tjre...@udel.edu> added the comment: 2.5 is closed to fixes other than security fixes. So this needs to be checked with the latest 2.6.
The implementation of new features does not always exactly follow the PEP. So if there is also no warning in 2.6, the question remains whether accident or intention. Perhaps it was decided that the warning was too difficult or that it would make too much noise because some people were doing this intentionally and would not want the warning, whereas few people accidentally do the sort of thing your example does. If this is true, as I sort of suspect, the PEP should be revised not to mislead. ---------- nosy: +tjreedy _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6580> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
