warnings should provide a public API for accessing its option parsing code

Open
#52,224 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Read the warnings module's option-parsing implementation and the linked warnings_opt_parse_API patches first, since the issue does not name a current source file or test. Done requires an agreed public API for this parsing behavior, documented semantics, and coverage for the exposed interface.

Written by the indexing model from the issue text.

Description

stdlib type-feature
BPO 7976
Nosy @brettcannon, @ncoghlan, @vstinner, @ericvsmith, @merwok, @bitdancer, @masklinn, @berkerpeksag
Files
  • warnings-option.diff: Addition of an Option instance to warnings for python 2's trunk.
  • warnings_opt_parse_API.patch: Expose command line parsing facilities
  • warnings_opt_parse_API-2.patch: Added doc.
  • warnings_opt_parse_API-3.patch
  • warnings_opt_parse_API-4.patch: Removed old private exception and function. Typo in the doc
  • warnings_opt_parse_API-5.patch: WarningsOptParsingError -> WarningsOptionParsingError + cosmetics
  • warnings_opt_parse_API-6.patch: renamed the function to parse_option
  • warnings_opt_parse_API-7.patch
    		•

    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-02-21.16:55:32.650>
labels = ['type-feature', 'library']
title = 'warnings should provide a public API for accessing its option parsing code'
updated_at = <Date 2019-07-29.11:30:38.903>
user = 'https://github.com/masklinn'

    bugs.python.org fields:

    activity = <Date 2019-07-29.11:30:38.903>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-02-21.16:55:32.650>
creator = 'xmorel'
dependencies = []
files = ['16279', '28153', '28154', '28158', '28160', '28173', '28174', '28175']
hgrepos = ['161']
issue_num = 7976
keywords = ['patch']
message_count = 19.0
messages = ['99670', '99893', '99896', '99897', '99921', '99930', '176607', '176608', '176610', '176615', '176624', '176628', '176630', '176639', '176723', '176730', '176731', '176735', '348615']
nosy_count = 9.0
nosy_names = ['brett.cannon', 'ncoghlan', 'vstinner', 'eric.smith', 'eric.araujo', 'r.david.murray', 'xmorel', 'berker.peksag', 'bruno.dupuis']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue7976'
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.