[issue11350] __setitem__()'s problem of dbm.dumb object pointed out by comments

[R. David Murray]

R. David Murray <rdmurray at bitdance.com> added the comment:

Well, I don't think we are going to add an abort method in order to write a unit test, though it isn't completely out of the question.

However, I've now looked at the code and the other comments in the file, and it is clear that great care is taken to allow the database to be out of sync in order to avoid calling _commit all the time.  So I don't think this is a desired change.

Thanks for working out the test, though, since it makes it clear that it is only a catastrophic failure of the interpreter that will trigger this bug (or, of course, a kill -KILL), and I think we are just accepting that danger.

If you disagree, it should be brought up on python-dev.

----------
resolution:  -> wont fix
stage: test needed -> committed/rejected
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue11350>
_______________________________________