posix_access swallows all errors

Open
#54,967 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the posix_access entry point in the Lib component and read the linked BPO issue and its discussion. Determine which errors are currently swallowed and which should remain visible; done means an agreed behavior is implemented with regression coverage in the relevant library tests.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 10758
Nosy @loewis, @birkenfeld, @pitrou

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 2010-12-22.12:45:08.599>
labels = ['type-feature', 'library']
title = 'posix_access swallows all errors'
updated_at = <Date 2010-12-22.20:16:54.361>
user = 'https://github.com/birkenfeld'

bugs.python.org fields:

activity = <Date 2010-12-22.20:16:54.361>
actor = 'loewis'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-12-22.12:45:08.599>
creator = 'georg.brandl'
dependencies = []
files = []
hgrepos = []
issue_num = 10758
keywords = []
message_count = 3.0
messages = ['124500', '124517', '124520']
nosy_count = 4.0
nosy_names = ['loewis', 'georg.brandl', 'pitrou', 'rosslagerwall']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue10758'
versions = ['Python 3.3']

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.