[easy C] long type performance waste in 64-bit Windows build
Open
Nobody has claimed this yet.
3.12
OS-windows
performance
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42304 |
|---|---|
| Nosy | @pfmoore, @vstinner, @tjguk, @zware, @serhiy-storchaka, @zooba, @animalize |
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 2020-11-10.07:33:14.971>
labels = ['3.10', 'OS-windows', 'performance']
title = '[easy C] long type performance waste in 64-bit Windows build'
updated_at = <Date 2020-11-10.10:33:09.880>
user = 'https://github.com/animalize'
bugs.python.org fields:
activity = <Date 2020-11-10.10:33:09.880>
actor = 'malin'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Windows']
creation = <Date 2020-11-10.07:33:14.971>
creator = 'malin'
dependencies = []
files = []
hgrepos = []
issue_num = 42304
keywords = []
message_count = 6.0
messages = ['380638', '380642', '380644', '380646', '380647', '380649']
nosy_count = 7.0
nosy_names = ['paul.moore', 'vstinner', 'tim.golden', 'zach.ware', 'serhiy.storchaka', 'steve.dower', 'malin']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'performance'
url = 'https://bugs.python.org/issue42304'
versions = ['Python 3.10']
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
No source file or test is named. Start by examining the 64-bit Windows build code that handles the long type and identify where the reported performance waste occurs; done means the unnecessary cost is removed and the relevant Windows build or test checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100