textwrap should treat Unicode em-dash like ASCII em-dash

Open
#74,865 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the existing PR #2224 and the textwrap entry point to understand the proposed handling of Unicode and ASCII em dashes. Done means textwrap treats the Unicode em dash like the ASCII em dash, with the relevant behavior covered by tests.

Written by the indexing model from the issue text.

Description

stdlib topic-unicode type-feature
BPO 30680
Nosy @bitdancer, @methane, @jonathaneunice
PRs
  • python/cpython#2224
    		•

    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 2017-06-15.19:09:00.240>
labels = ['type-feature', 'library', '3.10']
title = 'textwrap should treat Unicode em-dash like ASCII em-dash'
updated_at = <Date 2020-10-21.04:33:09.340>
user = 'https://github.com/jonathaneunice'

    bugs.python.org fields:

    activity = <Date 2020-10-21.04:33:09.340>
actor = 'methane'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-06-15.19:09:00.240>
creator = 'jonathaneunice'
dependencies = []
files = []
hgrepos = []
issue_num = 30680
keywords = []
message_count = 4.0
messages = ['296124', '296126', '296127', '379189']
nosy_count = 3.0
nosy_names = ['r.david.murray', 'methane', 'jonathaneunice']
pr_nums = ['2224']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30680'
versions = ['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.