No Instantiation Restrictions for AbstractBaseClasses derived from builtin types
Open
Nobody has claimed this yet.
3.10
3.11
3.9 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37927 |
|---|---|
| Nosy | @rhettinger, @tirkarthi, @iritkatriel, @AlexWaygood |
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 2019-08-23.07:51:55.787>
labels = ['interpreter-core', 'type-bug', '3.9', '3.10', '3.11']
title = 'No Instantiation Restrictions for AbstractBaseClasses derived from builtin types'
updated_at = <Date 2021-12-06.13:55:49.892>
user = 'https://bugs.python.org/TalhaAhmed'
bugs.python.org fields:
activity = <Date 2021-12-06.13:55:49.892>
actor = 'AlexWaygood'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2019-08-23.07:51:55.787>
creator = 'Talha Ahmed'
dependencies = []
files = []
hgrepos = []
issue_num = 37927
keywords = []
message_count = 4.0
messages = ['350264', '350265', '407804', '407806']
nosy_count = 5.0
nosy_names = ['rhettinger', 'xtreak', 'Talha Ahmed', 'iritkatriel', 'AlexWaygood']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37927'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
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 reading the linked bugs.python.org issue 37927 and its four-message discussion. The migration names no source file, test, or entry point, so first clarify the intended instantiation restriction and locate the relevant interpreter-core tests. Done should be defined by an agreed behavior and corresponding regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100