[getpass] Implement a "strict" mode for getuser()
Open
Nobody has claimed this yet.
3.13
OS-windows
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 46631 |
|---|---|
| Nosy | @pfmoore, @tjguk, @zware, @eryksun, @zooba |
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-02-04.05:55:34.124>
labels = ['type-feature', 'library', 'OS-windows', '3.11']
title = 'Implement a "strict" mode for getpass.getuser()'
updated_at = <Date 2022-02-05.03:39:16.470>
user = 'https://github.com/eryksun'
bugs.python.org fields:
activity = <Date 2022-02-05.03:39:16.470>
actor = 'eryksun'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Windows']
creation = <Date 2022-02-04.05:55:34.124>
creator = 'eryksun'
dependencies = []
files = []
hgrepos = []
issue_num = 46631
keywords = []
message_count = 2.0
messages = ['412495', '412556']
nosy_count = 5.0
nosy_names = ['paul.moore', 'tim.golden', 'zach.ware', 'eryksun', 'steve.dower']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46631'
versions = ['Python 3.11']
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
The payload names the getpass.getuser() entry point but does not identify target files, tests, or the strict-mode semantics. First clarify how strict behavior should differ from the current behavior, then locate the implementation and Windows-specific tests; done means the agreed behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100