Move captured_stdin(), captured_stdout(), and captured_stderr() to the public API.
Open
Nobody has claimed this yet.
3.9 (EOL)
tests
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40557 |
|---|---|
| Nosy | @terryjreedy, @felixxm |
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 2020-05-08.05:12:03.665>
labels = ['type-feature', 'tests', '3.9']
title = 'Move captured_stdin(), captured_stdout(), and captured_stderr() to the public API.'
updated_at = <Date 2020-05-08.22:55:48.097>
user = 'https://github.com/felixxm'
bugs.python.org fields:
activity = <Date 2020-05-08.22:55:48.097>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2020-05-08.05:12:03.665>
creator = 'felixxm'
dependencies = []
files = []
hgrepos = []
issue_num = 40557
keywords = []
message_count = 4.0
messages = ['368419', '368420', '368478', '368481']
nosy_count = 2.0
nosy_names = ['terry.reedy', 'felixxm']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue40557'
versions = ['Python 3.9']
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
Search the test support code for captured_stdin(), captured_stdout(), and captured_stderr(), then inspect their current callers and related tests. Confirm the intended public location from existing API conventions before making changes; done means the three helpers are available through the public API and the affected tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100