tkinter: change API of non-functioning peer_create, does not instantiate Text
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reviewing pythonlevelpeers.py, issue17945.diff, and peerfix.diff to understand the proposed peer_create API and the Text-instantiation problem. Compare the patch approaches with the current Tkinter behavior; done means the API change works and peer_create correctly instantiates Text without breaking related peers.
Written by the indexing model from the issue text.
Description
| BPO | 17945 |
|---|---|
| Nosy | @terryjreedy, @roseman, @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 2013-05-09.14:36:22.353>
labels = ['type-feature', 'expert-tkinter']
title = 'tkinter: change API of non-functioning peer_create, does not instantiate Text'
updated_at = <Date 2015-08-28.20:07:37.285>
user = 'https://bugs.python.org/ghoul'
bugs.python.org fields:
activity = <Date 2015-08-28.20:07:37.285>
actor = 'markroseman'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tkinter']
creation = <Date 2013-05-09.14:36:22.353>
creator = 'ghoul'
dependencies = []
files = ['30183', '30205', '30254']
hgrepos = []
issue_num = 17945
keywords = ['patch']
message_count = 12.0
messages = ['188778', '188782', '188784', '188787', '188872', '188908', '188932', '189174', '248956', '248966', '249293', '249295']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'gpolo', 'markroseman', 'serhiy.storchaka', 'ghoul']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17945'
versions = ['Python 3.6']
- 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