assertEqual doesn't display newline differences quite well

Open
#56,247 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the linked issue-12038.patch and the current assertEqual behavior in CPython. Reproduce a comparison between strings containing different newlines, then determine the expected human-readable output; the issue is done when newline differences are displayed clearly without changing other assertion behavior.

Written by the indexing model from the issue text.

Description

3.13 3.14 3.15 stdlib type-bug
BPO 12038
Nosy @terryjreedy, @gpshead, @pitrou, @ezio-melotti, @voidspace, @iritkatriel
Files
  • issue-12038.patch: Print a more human readable assert message when two strings don't match.
    		•

    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 = 'https://github.com/voidspace'
closed_at = None
created_at = <Date 2011-05-09.16:36:50.398>
labels = ['type-bug', 'library', '3.11']
title = "assertEqual doesn't display newline differences quite well"
updated_at = <Date 2021-12-09.21:45:16.085>
user = 'https://github.com/pitrou'

    bugs.python.org fields:

    activity = <Date 2021-12-09.21:45:16.085>
actor = 'iritkatriel'
assignee = 'michael.foord'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2011-05-09.16:36:50.398>
creator = 'pitrou'
dependencies = []
files = ['22486']
hgrepos = []
issue_num = 12038
keywords = ['patch']
message_count = 7.0
messages = ['135608', '135657', '135953', '136007', '136079', '139190', '408160']
nosy_count = 7.0
nosy_names = ['terry.reedy', 'gregory.p.smith', 'pitrou', 'ezio.melotti', 'michael.foord', 'mouad', 'iritkatriel']
pr_nums = []
priority = 'low'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue12038'
versions = ['Python 3.11']

    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.