libc_ver() runtime error when sys.executable is empty
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46338 |
|---|---|
| Nosy | @malemburg |
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 2022-01-10.22:01:51.436>
labels = ['3.9', 'type-crash']
title = 'libc_ver() runtime error when sys.executable is empty'
updated_at = <Date 2022-01-12.00:56:44.897>
user = 'https://bugs.python.org/alliehammond'
bugs.python.org fields:
activity = <Date 2022-01-12.00:56:44.897>
actor = 'allie.hammond'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2022-01-10.22:01:51.436>
creator = 'allie.hammond'
dependencies = []
files = []
hgrepos = []
issue_num = 46338
keywords = []
message_count = 3.0
messages = ['410261', '410283', '410372']
nosy_count = 2.0
nosy_names = ['lemburg', 'allie.hammond']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue46338'
versions = ['Python 3.9']
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 locating the libc_ver() implementation and its existing tests, then inspect the path taken when sys.executable is empty. Reproduce the runtime error in that condition and update the behavior so the call completes without the reported error, with a regression test covering the empty value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100