Gregory P. Smith greg at krypto.org
Mon Apr 2 18:49:37 EDT 2018

• Previous message (by thread): [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?
• Next message (by thread): [Python-Dev] building extensions as builtins is broken in 3.7
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Given that, go ahead and change in master (3.8).

On Mon, Apr 2, 2018 at 3:13 PM Christian Heimes <christian at python.org>
wrote:

> On 2018-04-02 22:48, Lukasz Langa wrote:
> > Pickle protocol version 4.0 was originally defined back in PEP 3154 and
> shipped as part of Python 3.4 back in 2011. Yet it's still not the default.
> There's a number of things that would run faster with it like
> multiprocessing.
> >
> > This is too late for 3.7 which is a shame but can we at least bump it
> for 3.8?
>
> It sounds like a reasonable request. Python 3.4 is out of commission by
> then. I'm sure the release manager for 3.8 is going to agree with you,
> too. :)
>
> Christian
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/greg%40krypto.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20180402/d5e82246/attachment.html>

---

• Previous message (by thread): [Python-Dev] Why is pickle.DEFAULT_PROTOCOL still 3?
• Next message (by thread): [Python-Dev] building extensions as builtins is broken in 3.7
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list