Hagen Fürstenau <hfuerste...@gmx.net> added the comment: Does that mean that nested() can be removed or changed incompatibly in 3.2 at the same time that an alternative way for handling the remaining use case is introduced?
This would seem to violate the promise in PEP 5, that "users will have at least a year to test their programs and migrate them from use of the deprecated construct to the alternative one". ---------- nosy: +hagen _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6288> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
