Define PY_UINT64_T on Windows 32bit
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
The issue names no source files or tests. Start by locating the interpreter-core definitions of PY_UINT64_T and the Windows 32-bit build configuration, then compare how the type is defined on other platforms. Done means the type is defined correctly for Windows 32-bit and the relevant build or test checks pass.
Written by the indexing model from the issue text.
Description
| BPO | 19433 |
|---|---|
| Nosy | @tim-one, @loewis, @ncoghlan, @vstinner, @tiran, @tjguk |
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-10-29.13:50:22.732>
labels = ['interpreter-core', 'type-feature', 'OS-windows']
title = 'Define PY_UINT64_T on Windows 32bit'
updated_at = <Date 2019-03-15.23:07:05.990>
user = 'https://github.com/tiran'
bugs.python.org fields:
activity = <Date 2019-03-15.23:07:05.990>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Windows']
creation = <Date 2013-10-29.13:50:22.732>
creator = 'christian.heimes'
dependencies = []
files = []
hgrepos = []
issue_num = 19433
keywords = []
message_count = 10.0
messages = ['201635', '201637', '201642', '201644', '201650', '201651', '201652', '201654', '201656', '235864']
nosy_count = 7.0
nosy_names = ['tim.peters', 'loewis', 'ncoghlan', 'vstinner', 'christian.heimes', 'tim.golden', 'python-dev']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19433'
versions = ['Python 3.4']
- 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