Ethan Furman added the comment: Can we do that? If a doc change can make it so we're not locked in to supporting __getnewargs__ I could live with that.
Although, to be honest, I'd rather get the change in *and* have a doc warning that pickling specifics are subject to change in 3.5. Really, getting rid of __getnewargs__ and going with just __reduce_ex__ is a change that started in issue20534, but at that point I still didn't totally grok __reduce_ex__ et al and so didn't complete the change there. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20679> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
