summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTim Peters <tim.peters@gmail.com>2003-01-30 16:35:08 (GMT)
committerTim Peters <tim.peters@gmail.com>2003-01-30 16:35:08 (GMT)
commit2b93c4c70820d0314e8e297c2817d9e03d73df62 (patch)
tree66da0ef1f9be0fc51aee913d97c6cc2c5794e32a
parentd01c1e91c43bdfd8d9107cc605a848c326f75e92 (diff)
downloadcpython-2b93c4c70820d0314e8e297c2817d9e03d73df62.zip
cpython-2b93c4c70820d0314e8e297c2817d9e03d73df62.tar.gz
cpython-2b93c4c70820d0314e8e297c2817d9e03d73df62.tar.bz2
Updated the INST/OBJ docs, to say they really are (almost) identical
in 2.3.
-rw-r--r--Lib/pickletools.py6
1 files changed, 6 insertions, 0 deletions
diff --git a/Lib/pickletools.py b/Lib/pickletools.py
index 7eaa1a5..74ba8d9 100644
--- a/Lib/pickletools.py
+++ b/Lib/pickletools.py
@@ -1614,6 +1614,8 @@ opcodes = [
the class object obtained from INST's arguments is applied to the
argtuple obtained from the stack, and the resulting instance object
is pushed on the stack.
+
+ NOTE: checks for __safe_for_unpickling__ went away in Python 2.3.
"""),
I(name='OBJ',
@@ -1643,6 +1645,10 @@ opcodes = [
except that no __safe_for_unpickling__ check is done (XXX this is
a bug; cPickle does test __safe_for_unpickling__). See INST for
the gory details.
+
+ NOTE: In Python 2.3, INST and OBJ are identical except for how they
+ get the class object. That was always the intent; the implementations
+ had diverged for accidental reasons.
"""),
I(name='NEWOBJ',