diff options
| author | Tim Peters <tim.peters@gmail.com> | 2003-01-27 19:38:34 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2003-01-27 19:38:34 (GMT) |
| commit | 1996e23054f2ac79cf89c9ef04714f336b0a17ce (patch) | |
| tree | 3ded4faef00f1af4e1613c71b2046244c3cb3d6a /Lib/pickletools.py | |
| parent | d916cf4ec7014e9f6b25b8d63728bda01a17d3f9 (diff) | |
| download | cpython-1996e23054f2ac79cf89c9ef04714f336b0a17ce.zip cpython-1996e23054f2ac79cf89c9ef04714f336b0a17ce.tar.gz cpython-1996e23054f2ac79cf89c9ef04714f336b0a17ce.tar.bz2 | |
Repaired comment.
Diffstat (limited to 'Lib/pickletools.py')
| -rw-r--r-- | Lib/pickletools.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Lib/pickletools.py b/Lib/pickletools.py index eda6d46..f7cebe3 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. |