From: Tim Peters Date: Mon, 27 Jan 2003 19:38:34 +0000 (+0000) Subject: Repaired comment. X-Git-Tag: v2.3c1~2284 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1996e23054f2ac79cf89c9ef04714f336b0a17ce;p=thirdparty%2FPython%2Fcpython.git Repaired comment. --- diff --git a/Lib/pickletools.py b/Lib/pickletools.py index eda6d466d292..f7cebe3b69f3 100644 --- a/Lib/pickletools.py +++ b/Lib/pickletools.py @@ -70,8 +70,8 @@ At heart, that's all the PM has. Subtleties arise for these reasons: + Backward compatibility and micro-optimization. As explained below, pickle opcodes never go away, not even when better ways to do a thing get invented. The repertoire of the PM just keeps growing over time. - So, e.g., there are now six distinct opcodes for building a Python integer, - five of them devoted to "short" integers. Even so, the only way to pickle + So, e.g., there are now five distinct opcodes for building a Python integer, + four of them devoted to "short" integers. Even so, the only way to pickle a Python long int takes time quadratic in the number of digits, for both pickling and unpickling. This isn't so much a subtlety as a source of wearying complication.