Turtle.onclick events blocked by Turtle.stamp
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 28264 |
|---|---|
| Nosy | @terryjreedy |
| 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 2016-09-24.02:36:39.910>
labels = ['3.7', 'type-bug', 'library']
title = 'Turtle.onclick events blocked by Turtle.stamp'
updated_at = <Date 2016-10-05.00:10:34.817>
user = 'https://bugs.python.org/GeorgeFagin'
bugs.python.org fields:
activity = <Date 2016-10-05.00:10:34.817>
actor = 'George Fagin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2016-09-24.02:36:39.910>
creator = 'George Fagin'
dependencies = []
files = ['44800']
hgrepos = []
issue_num = 28264
keywords = []
message_count = 5.0
messages = ['277306', '277767', '277929', '277933', '278096']
nosy_count = 2.0
nosy_names = ['terry.reedy', 'George Fagin']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue28264'
versions = ['Python 3.5', 'Python 3.6', 'Python 3.7']
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
Run the attached click_and_stamp.py sample first to reproduce the interaction between Turtle.onclick and Turtle.stamp. Then trace the relevant turtle-library event and stamping behavior; done means clicks still trigger the registered handler after stamping, with regression coverage for the demonstrated case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100