8000 Eliminate legacy checks in `curses.__init__` · Issue #133575 · python/cpython · GitHub
[go: up one dir, main page]

Skip to content
Eliminate legacy checks in curses.__init__ #133575
Closed
@picnixz

Description

@picnixz

Feature or enhancement

Proposal:

Some checks in curses.__init__ are now obsolete, essentially because of how the C functions are now implemented. For instance, start_color() checks for whether _curses.COLORS exists, but it will always exist if the call to _curses.start_color() succeeds.

Has this already been discussed elsewhere?

This is a minor feature, which does not need previous discussion elsewhere

Links to previous discussion of this feature:

No response

Linked PRs

Metadata

Metadata

Assignees

Labels

stdlibPython modules in the Lib dirtype-featureA feature request or enhancement

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0