Changing cls.__bases__ must ensure proper metaclass inheritance
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
No source files, tests, or entry points are identified; begin by reviewing the linked BPO issue and the interpreter-core implementation related to changing bases. Establish the failing metaclass-inheritance behavior and add coverage for the corrected behavior, with the work complete when that regression passes.
Written by the indexing model from the issue text.
Description
| BPO | 21919 |
|---|---|
| Nosy | @gvanrossum, @rhettinger, @tirkarthi |
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 = 'https://github.com/gvanrossum'
closed_at = None
created_at = <Date 2014-07-04.20:45:25.320>
labels = ['interpreter-core', 'type-bug', '3.8']
title = 'Changing cls.__bases__ must ensure proper metaclass inheritance'
updated_at = <Date 2018-09-28.18:34:40.580>
user = 'https://bugs.python.org/abusalimov'
bugs.python.org fields:
activity = <Date 2018-09-28.18:34:40.580>
actor = 'gvanrossum'
assignee = 'gvanrossum'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2014-07-04.20:45:25.320>
creator = 'abusalimov'
dependencies = []
files = []
hgrepos = []
issue_num = 21919
keywords = []
message_count = 6.0
messages = ['222312', '236753', '237072', '326532', '326650', '326651']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'rhettinger', 'abusalimov', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21919'
versions = ['Python 3.8']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100