Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters

Open
#69,462 8 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
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation, internationalization

Research direction

Start with the original BPO issue 25275 and compare the documented rules for integer literals with Python's behavior for non-ASCII characters. The payload names no files or tests, so first locate the relevant documentation and interpreter behavior; done means the documented behavior and actual behavior agree.

Written by the indexing model from the issue text.

Description

docs interpreter-core topic-unicode type-bug
BPO 25275
Nosy @vstinner, @ezio-melotti, @bitdancer, @vadmium

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 2015-09-30.05:19:45.865>
labels = ['interpreter-core', 'type-bug', 'expert-unicode', 'docs']
title = 'Documentation v/s behaviour mismatch wrt integer literals containing non-ASCII characters'
updated_at = <Date 2015-10-01.04:07:07.422>
user = 'https://bugs.python.org/shreevatsa'

bugs.python.org fields:

activity = <Date 2015-10-01.04:07:07.422>
actor = 'martin.panter'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Interpreter Core', 'Unicode']
creation = <Date 2015-09-30.05:19:45.865>
creator = 'shreevatsa'
dependencies = []
files = []
hgrepos = []
issue_num = 25275
keywords = []
message_count = 8.0
messages = ['251915', '251930', '251932', '251965', '251966', '251967', '251968', '251991']
nosy_count = 6.0
nosy_names = ['vstinner', 'ezio.melotti', 'r.david.murray', 'docs@python', 'martin.panter', 'shreevatsa']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25275'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']

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.