➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ethan.furman
Recipients barry, eli.bendersky, ethan.furman, larry, serhiy.storchaka
Date 2014-02-21.05:24:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392960295.62.0.506918100372.issue20679@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2014-02-21 05:24:55ethan.furmansetrecipients: + ethan.furman, barry, larry, eli.bendersky, serhiy.storchaka
2014-02-21 05:24:55ethan.furmansetmessageid: <1392960295.62.0.506918100372.issue20679@psf.upfronthosting.co.za>
2014-02-21 05:24:55ethan.furmanlinkissue20679 messages
2014-02-21 05:24:55ethan.furmancreate