Nick Coghlan <ncogh...@gmail.com> added the comment: That's a good point actually - with 3.1's "in-between" status and the lack of deprecation in 2.6, nested() is going to have to stick around for 2.7/3.2 anyway.
So PendingDeprecation now with full deprecation in 2.7/3.2 when we will hopefully have a better alternative in place is probably the way to go. Updating the docs to cover only the recommended use case is still something I want to do this week though (hopefully tomorrow). ---------- _______________________________________ 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
