Inability to specific __qualname__ as a property on a class instance.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reading the linked BPO issue 19073 and the Python Interpreter Core implementation related to qualname. The payload names no source files or tests, so locate the relevant behavior before deciding on an implementation. Done means the requested ability to specify qualname on a class instance is supported and covered by appropriate tests.
Written by the indexing model from the issue text.
Description
| BPO | 19073 |
|---|---|
| Nosy | @pitrou, @vstinner, @LewisGaul, @iritkatriel |
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-09-22.13:37:01.145>
labels = ['interpreter-core', 'type-feature', '3.11']
title = 'Inability to specific __qualname__ as a property on a class instance.'
updated_at = <Date 2022-01-25.23:29:35.829>
user = 'https://bugs.python.org/grahamd'
bugs.python.org fields:
activity = <Date 2022-01-25.23:29:35.829>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2013-09-22.13:37:01.145>
creator = 'grahamd'
dependencies = []
files = []
hgrepos = []
issue_num = 19073
keywords = []
message_count = 5.0
messages = ['198275', '198276', '387431', '409960', '411687']
nosy_count = 5.0
nosy_names = ['pitrou', 'vstinner', 'grahamd', 'LewisGaul', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19073'
versions = ['Python 3.11']
- 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