Wording tweaks
This commit is contained in:
parent
a4b740aacb
commit
554b1b0f9c
|
@ -106,8 +106,8 @@ as bound methods, is implemented in the multiprocessing module [5]_.
|
|||
|
||||
The ``__qualname__`` attribute from :pep:`3155` makes it possible to
|
||||
lookup many more objects by name. Making the GLOBAL_STACK opcode accept
|
||||
dot-separated names, or adding a special GETATTR opcode, would allow the
|
||||
standard pickle implementation to support all those kinds of objects.
|
||||
dot-separated names would allow the standard pickle implementation to
|
||||
support all those kinds of objects.
|
||||
|
||||
64-bit opcodes for large objects
|
||||
--------------------------------
|
||||
|
@ -132,7 +132,7 @@ Calling __new__ with keyword arguments
|
|||
|
||||
Currently, classes whose __new__ mandates the use of keyword-only
|
||||
arguments can not be pickled (or, rather, unpickled) [3]_. Both a new
|
||||
special method (``__getnewargs_ex__`` ?) and a new opcode (NEWOBJEX ?)
|
||||
special method (``__getnewargs_ex__`` ?) and a new opcode (NEWOBJ_EX ?)
|
||||
are needed.
|
||||
|
||||
Better string encoding
|
||||
|
@ -146,6 +146,9 @@ would make many pickles smaller.
|
|||
Summary of new opcodes
|
||||
======================
|
||||
|
||||
These reflect the state of the proposed implementation (thanks mostly
|
||||
to Alexandre Vassalotti's work):
|
||||
|
||||
* ``SHORT_BINUNICODE``: push a utf8-encoded str object with a one-byte
|
||||
size prefix (therefore less than 256 bytes long).
|
||||
|
||||
|
|
Loading…
Reference in New Issue