Shelve sync issues while using Gevent

Open
#79,805 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
databases

Research direction

Start by reviewing linked PRs gh-127507 and gh-137997, then inspect the shelve library behavior involved in Gevent use. Done means the synchronization issue is addressed and covered by the relevant tests, but the issue names no files or test paths.

Written by the indexing model from the issue text.

Description

3.13 3.14 3.15 docs stdlib triaged
BPO 35624
Nosy @rhettinger, @terryjreedy, @vstinner, @remilapeyre

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2018-12-31.08:12:16.504>
labels = ['3.8', 'type-bug', 'library']
title = 'Shelve sync issues while using Gevent'
updated_at = <Date 2019-01-07.15:16:09.720>
user = 'https://bugs.python.org/OdedEngel'

bugs.python.org fields:

activity = <Date 2019-01-07.15:16:09.720>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-12-31.08:12:16.504>
creator = 'Oded Engel'
dependencies = []
files = []
hgrepos = []
issue_num = 35624
keywords = []
message_count = 4.0
messages = ['332807', '332809', '332994', '333038']
nosy_count = 5.0
nosy_names = ['rhettinger', 'terry.reedy', 'vstinner', 'remi.lapeyre', 'Oded Engel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue35624'
versions = ['Python 3.8']

Linked PRs
  • gh-127507
  • gh-137997
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.