Format parser is too permissive

Open
#54,230 11 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
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

No source file, test, or entry point is named. Start with the linked BPO issue 10021 and its migrated 11-comment history, then identify the format-parser behavior and documentation location discussed there; done requires an agreed fix for the permissiveness concern and verification of the affected cases.

Written by the indexing model from the issue text.

Description

docs type-bug
BPO 10021
Nosy @terryjreedy, @mdickinson, @abalkin, @ericvsmith, @benjaminp, @merwok

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 2010-10-04.16:24:04.133>
labels = ['type-bug', 'docs']
title = 'Format parser is too permissive'
updated_at = <Date 2015-10-02.21:38:35.279>
user = 'https://github.com/abalkin'

bugs.python.org fields:

activity = <Date 2015-10-02.21:38:35.279>
actor = 'belopolsky'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2010-10-04.16:24:04.133>
creator = 'belopolsky'
dependencies = []
files = []
hgrepos = []
issue_num = 10021
keywords = []
message_count = 11.0
messages = ['117961', '117964', '117965', '117966', '117967', '117969', '117971', '117992', '118009', '118011', '118232']
nosy_count = 7.0
nosy_names = ['terry.reedy', 'mark.dickinson', 'belopolsky', 'eric.smith', 'benjamin.peterson', 'eric.araujo', 'docs@python']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue10021'
versions = ['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.