Demian Brecht added the comment: On 2015-01-28 7:41 AM, R. David Murray wrote: > Although they are private interfaces we may decide we need a deprecation > release before dropping them. Sometimes what we do in cases like this is go > ahead and make the changes, but also provide the old methods via a > backward-compatible shim and have them emit deprecation warnings.
That makes sense. If it's decided that's the path that should be pursued, I'll add them in once the functional/test/doc changes have all been made. Thanks for the heads up. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23334> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
