ttk.TreeView (and maybe other functions) is overzealous in converting item values to ints
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
topic-tkinter
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34447 |
|---|---|
| Nosy | @serhiy-storchaka |
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-08-21.04:49:03.443>
labels = ['3.8', '3.7', 'expert-tkinter']
title = 'ttk.TreeView (and maybe other functions) is overzealous in converting item values to ints'
updated_at = <Date 2018-08-21.05:53:15.100>
user = 'https://bugs.python.org/abarnert'
bugs.python.org fields:
activity = <Date 2018-08-21.05:53:15.100>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tkinter']
creation = <Date 2018-08-21.04:49:03.443>
creator = 'abarnert'
dependencies = []
files = []
hgrepos = []
issue_num = 34447
keywords = []
message_count = 1.0
messages = ['323819']
nosy_count = 2.0
nosy_names = ['serhiy.storchaka', 'abarnert']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue34447'
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 locating the ttk.TreeView implementation in the Tkinter component and inspect how item values are converted to integers. Compare the behavior with the issue's reported over-conversion and determine whether other functions are affected. Done means the intended values are preserved and the behavior is covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100