The pwd module doesn't distinguish between errors and no user

Open
#48,511 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
operating-systems

Research direction

Start by reviewing the pwd module and the linked PR gh-102223, then locate the tests covering its error and no-user behavior. Done means the module distinguishes those outcomes and the relevant tests pass.

Written by the indexing model from the issue text.

Description

easy extension-modules type-bug
BPO 4261
Nosy @vstinner, @bitdancer

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 2008-11-05.08:19:21.716>
labels = ['extension-modules', 'easy', 'type-bug']
title = "The pwd module doesn't distinguish between errors and no user"
updated_at = <Date 2014-03-23.17:59:38.828>
user = 'https://bugs.python.org/astrand'

bugs.python.org fields:

activity = <Date 2014-03-23.17:59:38.828>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2008-11-05.08:19:21.716>
creator = 'astrand'
dependencies = []
files = []
hgrepos = []
issue_num = 4261
keywords = ['easy']
message_count = 11.0
messages = ['75516', '75519', '101505', '101506', '214528', '214557', '214566', '214574', '214584', '214615', '214623']
nosy_count = 4.0
nosy_names = ['astrand', 'vstinner', 'r.david.murray', 'BreamoreBoy']
pr_nums = []
priority = 'normal'
resolution = 'accepted'
stage = 'test needed'
status = 'languishing'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue4261'
versions = ['Python 3.5']

Linked PRs
  • gh-102223
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.