object.__new__ does not accept arguments if __bases__ is changed
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
interpreter-core
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32768 |
|---|---|
| Nosy | @gvanrossum, @ncoghlan, @bitdancer, @ethanfurman, @serhiy-storchaka |
| 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 2018-02-04.22:05:12.953>
labels = ['interpreter-core', '3.8', 'type-bug', '3.7']
title = 'object.__new__ does not accept arguments if __bases__ is changed'
updated_at = <Date 2020-12-24.20:00:05.366>
user = 'https://bugs.python.org/VA'
bugs.python.org fields:
activity = <Date 2020-12-24.20:00:05.366>
actor = 'ethan.furman'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2018-02-04.22:05:12.953>
creator = 'VA'
dependencies = []
files = ['47425']
hgrepos = []
issue_num = 32768
keywords = []
message_count = 12.0
messages = ['311622', '311656', '311667', '311679', '311696', '311716', '311731', '311772', '341692', '341693', '341782', '383703']
nosy_count = 7.0
nosy_names = ['gvanrossum', 'ncoghlan', 'r.david.murray', 'ethan.furman', 'serhiy.storchaka', 'VA', 'alexey-muranov']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue32768'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
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 reproduction in bases.py and confirm the object.new behavior after changing bases. Then trace the relevant interpreter-core handling and review the linked BPO discussion to determine the intended behavior. Done means a focused regression test captures the case and the behavior is corrected without breaking existing object construction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100