Document getpass.getpass behavior on ^C

Open
#68,899 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Locate the documentation for getpass.getpass and inspect the behavior described by the issue title when ^C is entered. Document that behavior in the relevant Python documentation page. Done means the documentation accurately describes the current behavior; the payload names no specific file or test.

Written by the indexing model from the issue text.

Description

3.10 3.9 (EOL) docs
BPO 24711
Nosy @terryjreedy, @untitaker, @davidism, @iritkatriel

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 2015-07-24.23:12:11.819>
labels = ['3.9', '3.10', 'docs']
title = 'Document getpass.getpass behavior on ^C'
updated_at = <Date 2022-01-21.20:31:24.753>
user = 'https://github.com/untitaker'

bugs.python.org fields:

activity = <Date 2022-01-21.20:31:24.753>
actor = 'terry.reedy'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2015-07-24.23:12:11.819>
creator = 'untitaker'
dependencies = []
files = []
hgrepos = []
issue_num = 24711
keywords = []
message_count = 6.0
messages = ['247302', '382520', '384858', '410824', '410825', '411181']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'docs@python', 'untitaker', 'davidism', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'resolved'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue24711'
versions = ['Python 3.9', 'Python 3.10']

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.