Database corruption with the shelve module
Open
Nobody has claimed this yet.
3.10
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 47072 |
|---|---|
| Nosy | @malemburg, @terryjreedy, @koobs, @HubTou |
| Files |
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 2022-03-20.17:29:23.398>
labels = ['type-bug', '3.8', '3.10']
title = 'Database corruption with the shelve module'
updated_at = <Date 2022-03-27.12:01:09.272>
user = 'https://github.com/HubTou'
bugs.python.org fields:
activity = <Date 2022-03-27.12:01:09.272>
actor = 'Leilei'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Demos and Tools']
creation = <Date 2022-03-20.17:29:23.398>
creator = 'HubTou'
dependencies = []
files = ['50693', '50703', '50704']
hgrepos = []
issue_num = 47072
keywords = []
message_count = 7.0
messages = ['415625', '416036', '416045', '416063', '416108', '416110', '416119']
nosy_count = 4.0
nosy_names = ['lemburg', 'terry.reedy', 'koobs', 'HubTou']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue47072'
versions = ['Python 3.8', 'Python 3.10']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the attached shelve-test.zip reproduction and compare it with the shelve-test-3.10.zip results. Read the Python shelve module while confirming the corruption scenario; done means the reported database corruption is reproduced, understood, and prevented by a verified test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100