[New-bugs-announce] [issue26773] Shelve works inconsistently when carried over to child processes

Paul Ellenbogen report at bugs.python.org
Fri Apr 15 15:43:36 EDT 2016

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 the error. It may need to be run a few times.

If shelve is not meant to be inherited by the child process in this way, it should consistently throw an error (probably not a KeyError) on any use, including the first. This way it can be caught in the child, and the shelve can potentially be reopened in the child.

A current workaround is to find all places where a process may fork, and reopen any shelves in the child process after the fork. This may work for most smaller scripts. This could become tedious in more complex applications that fork in multiple places and open shelves in multiple places.



#!/usr/bin/env python3

import multiprocessing
import platform
import sys


3.4.3+ (default, Oct 14 2015, 16:03:50) 
[GCC 5.2.1 20151010]

components: Interpreter Core
files: shelve_process.py
messages: 263522
nosy: Paul Ellenbogen
priority: normal
severity: normal
status: open
title: Shelve works inconsistently when carried over to child processes
versions: Python 3.4, Python 3.5
Added file: http://bugs.python.org/file42475/shelve_process.py

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list