Christian, I don't know why you keep marking this bug as invalid. You were the one who committed the fix to ZODB 3.8 (https://bugs.edge.launchpad.net/zodb/+bug/153316), and this is exactly the same bug. This is the output of running the testcase that Matt attached against a stock python-zodb package:
Making empty database
storing an object...
inspecting object...
object still works...
committing transaction...
inspecting object...
object still works...
closing up zodb... done
opening for another look...
inspecting object...
object is broken!
done
and here's the output of the same testcase using a patched python-zodb package:
Christian, I don't know why you keep marking this bug as invalid. You were the one who committed the fix to ZODB 3.8 (https:/ /bugs.edge. launchpad. net/zodb/ +bug/153316), and this is exactly the same bug. This is the output of running the testcase that Matt attached against a stock python-zodb package:
Making empty database
storing an object...
inspecting object...
object still works...
committing transaction...
inspecting object...
object still works...
closing up zodb... done
opening for another look...
inspecting object...
object is broken!
done
and here's the output of the same testcase using a patched python-zodb package:
Making empty database
storing an object...
inspecting object...
object still works...
committing transaction...
inspecting object...
object still works...
closing up zodb... done
opening for another look...
inspecting object...
object still works...
done