summaryrefslogtreecommitdiffstats
path: root/Lib/dumbdbm.py
diff options
context:
space:
mode:
authorAndrew M. Kuchling <amk@amk.ca>2000-07-10 13:56:35 (GMT)
committerAndrew M. Kuchling <amk@amk.ca>2000-07-10 13:56:35 (GMT)
commita48dbde93b661372bb82e088672854c258dc6609 (patch)
tree95f1e0d8611e1f61a5a6a5eb4f7b8c059e40f630 /Lib/dumbdbm.py
parent39e0e5a180eb6c64a03806c18838d0083cc9f6f7 (diff)
downloadcpython-a48dbde93b661372bb82e088672854c258dc6609.zip
cpython-a48dbde93b661372bb82e088672854c258dc6609.tar.gz
cpython-a48dbde93b661372bb82e088672854c258dc6609.tar.bz2
Patch from Joe Eaton <jeaton@hostway.net> (SF#100741) to fix following problem:
There is a silly bug in the fall-back dumbdbm.py database package in the Python 1.5.2 standard distro. This bug causes any changes to an existing item to generate a new key, even when the key already exists. After many updates, the .dir file used by dumbdbm grows to a huge size, and can cause filesystem problems.
Diffstat (limited to 'Lib/dumbdbm.py')
-rw-r--r--Lib/dumbdbm.py1
1 files changed, 0 insertions, 1 deletions
diff --git a/Lib/dumbdbm.py b/Lib/dumbdbm.py
index 200bc7f..0ce901f 100644
--- a/Lib/dumbdbm.py
+++ b/Lib/dumbdbm.py
@@ -120,7 +120,6 @@ class _Database:
else:
pos, siz = self._addval(val)
self._index[key] = pos, siz
- self._addkey(key, (pos, siz))
def __delitem__(self, key):
del self._index[key]