PEP 574: Retitle "Alternatives" to "Rejected alternatives" (#696)
This commit is contained in:
parent
5232173ad6
commit
6482422d75
|
@ -359,8 +359,11 @@ This won't happen with the traditional ``pickle`` API (i.e. without passing
|
||||||
is serialized inside the pickle stream with a copy.
|
is serialized inside the pickle stream with a copy.
|
||||||
|
|
||||||
|
|
||||||
Alternatives
|
Rejected alternatives
|
||||||
============
|
=====================
|
||||||
|
|
||||||
|
Using the existing persistent load interface
|
||||||
|
--------------------------------------------
|
||||||
|
|
||||||
The ``pickle`` persistence interface is a way of storing references to
|
The ``pickle`` persistence interface is a way of storing references to
|
||||||
designated objects in the pickle stream while handling their actual
|
designated objects in the pickle stream while handling their actual
|
||||||
|
@ -414,7 +417,7 @@ Open questions
|
||||||
Should ``buffer_callback`` take a single buffers or a sequence of buffers?
|
Should ``buffer_callback`` take a single buffers or a sequence of buffers?
|
||||||
|
|
||||||
* Taking a single buffer would allow returning a boolean indicating whether
|
* Taking a single buffer would allow returning a boolean indicating whether
|
||||||
the given buffer is serialized in-band or out-of-band.
|
the given buffer should be serialized in-band or out-of-band.
|
||||||
* Taking a sequence of buffers is potentially more efficient by reducing
|
* Taking a sequence of buffers is potentially more efficient by reducing
|
||||||
function call overhead.
|
function call overhead.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue