RetroSearch Browse

Mon Nov 18 16:48:27 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-November/130325.html

On Mon, Nov 18, 2013 at 3:28 AM, Serhiy Storchaka <storchaka at gmail.com>wrote:

> 18.11.13 07:53, Tim Peters написав(ла):
>
>  - Some easy sanity checking due to the tiny redundancy (if the byte
>> immediately following the current frame is not a FRAME opcode, the
>> pickle is corrupt; and also corrupt if a FRAME opcode is encountered
>> _inside_ the current frame).
>>
>
> For efficient unpickling a FRAME opcode followed by 8-byte count should be
> *last* thing in a frame (unless it is a last frame).
>

I don't understand that.

Clearly the framing is the weakest point of the PEP (== elicits the most
bikeshedding). I am also unsure about the value of framing when pickles are
written to strings.

-- 
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20131118/2e1d4688/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-November/130325.html below:

[Python-Dev] Accepting PEP 3154 for 3.4?