Improve Unicode Documentation with Known Caveats

Open
#55,782 3 comments 0 reactions 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
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation, internationalization

Research direction

Start by reviewing the original BPO issue 11573 and the Unicode documentation area; the payload does not identify a specific file or test. Determine which Unicode caveats are still relevant and document them in the appropriate documentation pages. Done means the known caveats are clearly covered and the documentation builds successfully.

Written by the indexing model from the issue text.

Description

docs topic-unicode
BPO 11573
Nosy @vstinner, @mitsuhiko

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 2011-03-16.17:15:40.852>
labels = ['expert-unicode', 'docs']
title = 'Improve Unicode Documentation with Known Caveats'
updated_at = <Date 2011-03-17.23:37:21.430>
user = 'https://github.com/mitsuhiko'

bugs.python.org fields:

activity = <Date 2011-03-17.23:37:21.430>
actor = 'eric.araujo'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Unicode']
creation = <Date 2011-03-16.17:15:40.852>
creator = 'aronacher'
dependencies = []
files = []
hgrepos = []
issue_num = 11573
keywords = []
message_count = 2.0
messages = ['131143', '131291']
nosy_count = 3.0
nosy_names = ['vstinner', 'aronacher', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue11573'
versions = ['Python 3.1', 'Python 3.2', 'Python 3.3']

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.