python / python/cpython

pprint tests do not test pprint.pprint()

Open
#89,722 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tests type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Description

BPO 45559
Nosy @ericvsmith, @hp310780

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 2021-10-21.20:23:04.931>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'pprint tests do not test pprint.pprint()'
updated_at = <Date 2022-02-18.15:18:17.383>
user = 'https://github.com/ericvsmith'

bugs.python.org fields:

activity = <Date 2022-02-18.15:18:17.383>
actor = 'eric.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-10-21.20:23:04.931>
creator = 'eric.smith'
dependencies = []
files = []
hgrepos = []
issue_num = 45559
keywords = []
message_count = 3.0
messages = ['404647', '413484', '413486']
nosy_count = 2.0
nosy_names = ['eric.smith', 'hp310780']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45559'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Linked PRs
  • gh-95281

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.

Research direction

Start by locating the pprint test module and reviewing how the existing tests invoke the pprint functionality. Add coverage for the pprint.pprint() entry point, then run the relevant pprint tests and confirm they pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.