[issue26773] Shelve works inconsistently when carried over to child processes

Mark Kellogg added the comment: The gentoo user's version of gdbm is: gdbm-1.11 -- ___ Python tracker ___ ___

[issue26773] Shelve works inconsistently when carried over to child processes

Mark Kellogg added the comment: I have also been running into this issue. I am using Debian GNU/Linux 8, it was also reproduced on ubuntu by a coworker. It however was not reproducible on Gentoo in our testing. -- nosy: +mkellogg ___ Python

[issue26773] Shelve works inconsistently when carried over to child processes

Paul Ellenbogen added the comment: I think this behavior is due to the underlying behavior of the dbm. The same code using dbm, rather than shelve, also throws KeyErrors: from multiprocessing import Process import dbm db = dbm.open("example.dbm", "c") for i in range(100): db[str(i)] =

[issue26773] Shelve works inconsistently when carried over to child processes

Changes by SilentGhost : -- components: +Extension Modules nosy: +jnoller, sbt ___ Python tracker ___

[issue26773] Shelve works inconsistently when carried over to child processes

New submission from Paul Ellenbogen: If a shelve is opened, then the processed forked, sometime the shelve will appear to work in the child, and other times it will throw a KeyError. I suspect the order of element access may trigger the issue. I have included a python script that will exhibit