POSIX semantics of PATH search in execvpe is not respected

Open
#64,147 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start at the Library (Lib) implementation of execvpe and compare its PATH search behavior with the POSIX semantics described by the issue, within the recorded Python 2.7 scope. Done means execvpe's PATH search follows POSIX behavior and the affected behavior is verified.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 19948
Nosy @ericvsmith, @bitdancer, @ztane

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-12-10.14:55:25.783>
labels = ['type-bug', 'library']
title = 'POSIX semantics of PATH search in execvpe is not respected'
updated_at = <Date 2016-11-21.09:29:50.292>
user = 'https://bugs.python.org/glondu'

bugs.python.org fields:

activity = <Date 2016-11-21.09:29:50.292>
actor = 'ztane'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2013-12-10.14:55:25.783>
creator = 'glondu'
dependencies = []
files = []
hgrepos = []
issue_num = 19948
keywords = []
message_count = 10.0
messages = ['205819', '205850', '205899', '205900', '205908', '205909', '205910', '279943', '281335', '281338']
nosy_count = 5.0
nosy_names = ['eric.smith', 'r.david.murray', 'ztane', 'glondu', 'Alex Samuel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue19948'
versions = ['Python 2.7']

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.