str.isspace should use the Unicode White_Space property

Open
#62,436 24 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reviewing the linked pull request #16254 and the attached 42973dfea391.diff, then trace the existing str.isspace behavior in the interpreter. Done means str.isspace follows the Unicode White_Space property; use the pull request's discussion and changes to identify the expected verification.

Written by the indexing model from the issue text.

Description

3.9 (EOL) interpreter-core topic-unicode type-bug
BPO 18236
Nosy @malemburg, @loewis, @terryjreedy, @abalkin, @vstinner, @ezio-melotti, @bitdancer, @vadmium, @serhiy-storchaka, @animalize, @gnprice
PRs
  • python/cpython#16254
    		•
    Files
  • 42973dfea391.diff
    		•

    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 2013-06-17.01:06:30.764>
labels = ['interpreter-core', 'type-bug', '3.9', 'expert-unicode']
title = 'str.isspace should use the Unicode White_Space property'
updated_at = <Date 2019-09-18.06:02:16.653>
user = 'https://github.com/abalkin'

    bugs.python.org fields:

    activity = <Date 2019-09-18.06:02:16.653>
actor = 'Greg Price'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core', 'Unicode']
creation = <Date 2013-06-17.01:06:30.764>
creator = 'belopolsky'
dependencies = []
files = ['30680']
hgrepos = ['201']
issue_num = 18236
keywords = ['patch']
message_count = 18.0
messages = ['191303', '191612', '191647', '191648', '191649', '191650', '191652', '191687', '191689', '191706', '191739', '191746', '221919', '230183', '349213', '349214', '349233', '350414']
nosy_count = 11.0
nosy_names = ['lemburg', 'loewis', 'terry.reedy', 'belopolsky', 'vstinner', 'ezio.melotti', 'r.david.murray', 'martin.panter', 'serhiy.storchaka', 'malin', 'Greg Price']
pr_nums = ['16254']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue18236'
versions = ['Python 3.9']

    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.