On Tue, Aug 16, 2011 at 5:56 AM, Alexandre Vassalotti
wrote:
>
> On Fri, Aug 12, 2011 at 3:58 AM, Antoine Pitrou wrote:
>>
>> Hello,
>>
>> This PEP is an attempt to foster a number of small incremental
>> improvements in a future pickle protocol version. The PEP process is
>> used in order to gat
On Fri, Aug 12, 2011 at 3:58 AM, Antoine Pitrou wrote:
>
> Hello,
>
> This PEP is an attempt to foster a number of small incremental
> improvements in a future pickle protocol version. The PEP process is
> used in order to gather as many improvements as possible, because the
> introduction of a n
On Fri, Aug 12, 2011 at 3:58 AM, Antoine Pitrou wrote:
> This PEP is an attempt to foster a number of small incremental
> improvements in a future pickle protocol version. The PEP process is
> used in order to gather as many improvements as possible, because the
> introduction of a new protocol ve
Hello,
Le vendredi 12 août 2011 à 14:32 +0200, Xavier Morel a écrit :
> On 2011-08-12, at 12:58 , Antoine Pitrou wrote:
> > Current protocol versions export object sizes for various built-in types
> > (str, bytes) as 32-bit ints. This forbids serialization of large data
> > [1]_. New opcodes are
On 2011-08-12, at 12:58 , Antoine Pitrou wrote:
> Current protocol versions export object sizes for various built-in types
> (str, bytes) as 32-bit ints. This forbids serialization of large data
> [1]_. New opcodes are required to support very large bytes and str
> objects.
How about changing obje
Hello,
This PEP is an attempt to foster a number of small incremental
improvements in a future pickle protocol version. The PEP process is
used in order to gather as many improvements as possible, because the
introduction of a new protocol version should be a rare occurrence.
Feel free to sugges
