ctypes fails to find ncurses via ncursesw on Arch Linux
Open
Nobody has claimed this yet.
topic-ctypes
topic-curses
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27900 |
|---|---|
| Nosy | @amauryfa, @abalkin, @blueyed, @meadori |
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 2016-08-30.18:16:32.627>
labels = ['ctypes', 'type-bug']
title = 'ctypes fails to find ncurses via ncursesw on Arch Linux'
updated_at = <Date 2016-08-31.08:26:48.366>
user = 'https://github.com/blueyed'
bugs.python.org fields:
activity = <Date 2016-08-31.08:26:48.366>
actor = 'SilentGhost'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['ctypes']
creation = <Date 2016-08-30.18:16:32.627>
creator = 'blueyed'
dependencies = []
files = []
hgrepos = []
issue_num = 27900
keywords = []
message_count = 1.0
messages = ['273947']
nosy_count = 4.0
nosy_names = ['amaury.forgeotdarc', 'belopolsky', 'blueyed', 'meador.inge']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27900'
versions = ['Python 3.5']
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 reproducing the ctypes library lookup failure on Arch Linux and inspect how ncursesw is searched. The work is done when ctypes can find ncurses through ncursesw in that environment; the issue names no source file or test, so locating the relevant lookup code and regression coverage will require repository research.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100