is(upper/lower/title) are not exactly correct

Open
#58,030 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
internationalization

Research direction

The issue concerns Python's upper, lower, and title checks for Unicode, but it names no source files, tests, or concrete expected changes. Start by locating the string methods and their Unicode-related tests, then determine the intended behavior from the linked BPO issue and Unicode requirements; done means the affected checks are exactly correct with regression coverage.

Written by the indexing model from the issue text.

Description

interpreter-core topic-unicode type-feature
BPO 13822
Nosy @giampaolo, @benjaminp, @ezio-melotti, @tirkarthi

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 2012-01-19.04:22:54.269>
labels = ['type-feature', 'expert-unicode']
title = 'is(upper/lower/title) are not exactly correct'
updated_at = <Date 2018-09-22.16:28:32.920>
user = 'https://github.com/benjaminp'

bugs.python.org fields:

activity = <Date 2018-09-22.16:28:32.920>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2012-01-19.04:22:54.269>
creator = 'benjamin.peterson'
dependencies = []
files = []
hgrepos = []
issue_num = 13822
keywords = []
message_count = 1.0
messages = ['151606']
nosy_count = 4.0
nosy_names = ['giampaolo.rodola', 'benjamin.peterson', 'ezio.melotti', 'xtreak']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13822'
versions = ['Python 3.5']

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.