Drop restriction that meta.__prepare__() must return a dict (subclass)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the linked type-namespace-restriction.diff patch, then review the dependent issues bpo-17422 and bpo-31588 for related constraints and failure cases. Done means the restriction on meta.prepare() is addressed consistently and the relevant class-creation behavior is verified by tests.
Written by the indexing model from the issue text.
Description
| BPO | 17421 |
|---|---|
| Nosy | @loewis, @ncoghlan, @vstinner, @durban, @ericsnowcurrently, @serhiy-storchaka, @cdonovick |
| Dependencies | |
| 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 2013-03-14.20:20:27.737>
labels = ['type-feature']
title = 'Drop restriction that meta.__prepare__() must return a dict (subclass)'
updated_at = <Date 2019-03-12.22:17:10.507>
user = 'https://github.com/ericsnowcurrently'
bugs.python.org fields:
activity = <Date 2019-03-12.22:17:10.507>
actor = 'donovick'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2013-03-14.20:20:27.737>
creator = 'eric.snow'
dependencies = ['17422', '31588']
files = ['29408']
hgrepos = []
issue_num = 17421
keywords = ['patch']
message_count = 6.0
messages = ['184187', '184203', '184206', '184309', '303022', '337814']
nosy_count = 7.0
nosy_names = ['loewis', 'ncoghlan', 'vstinner', 'daniel.urban', 'eric.snow', 'serhiy.storchaka', 'donovick']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17421'
versions = ['Python 3.4']
- 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