Enable curses support on Windows

Open
#85,796 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
build-system, operating-systems

Research direction

The issue names no source files or tests. Start by reviewing linked PR gh-154956 and the migrated PR #21950, then inspect their changes and validation for Windows builds. Done means curses support is enabled on Windows and the relevant build or test checks pass.

Written by the indexing model from the issue text.

Description

build OS-windows topic-curses type-feature
BPO 41630
Nosy @pfmoore, @tjguk, @zware, @zooba, @madebr
PRs
  • python/cpython#21950
    		•

    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-08-25.04:15:19.157>
labels = ['3.10', 'type-feature', 'OS-windows', 'build']
title = 'Enable curses support on Windows'
updated_at = <Date 2020-08-25.17:05:55.513>
user = 'https://github.com/madebr'

    bugs.python.org fields:

    activity = <Date 2020-08-25.17:05:55.513>
actor = 'steve.dower'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Build', 'Windows']
creation = <Date 2020-08-25.04:15:19.157>
creator = 'maarten'
dependencies = []
files = []
hgrepos = []
issue_num = 41630
keywords = ['patch']
message_count = 2.0
messages = ['375871', '375894']
nosy_count = 5.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'steve.dower', 'maarten']
pr_nums = ['21950']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue41630'
versions = ['Python 3.10']

    Linked PRs
    • gh-154956
    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.