del _limbo[self] KeyError
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27908 |
|---|---|
| Nosy | @tim-one, @dimaqq, @rooterkyberian |
| 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 2016-08-31.07:27:38.972>
labels = ['3.7', 'type-bug', 'library']
title = 'del _limbo[self] KeyError'
updated_at = <Date 2016-09-15.19:35:06.916>
user = 'https://github.com/dimaqq'
bugs.python.org fields:
activity = <Date 2016-09-15.19:35:06.916>
actor = 'rooter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-08-31.07:27:38.972>
creator = 'Dima.Tisnek'
dependencies = []
files = ['44643', '44677']
hgrepos = []
issue_num = 27908
keywords = ['patch']
message_count = 6.0
messages = ['274005', '276325', '276331', '276333', '276337', '276605']
nosy_count = 3.0
nosy_names = ['tim.peters', 'Dima.Tisnek', 'rooter']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27908'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6', 'Python 3.7']
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
The issue concerns deleting _limbo[self] and includes issue27908.patch and issue27908_2.patch; start by reviewing those patches and the related library entry point. Reproduce the KeyError and verify that the library test suite no longer encounters it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100