python / python/cpython

Expose parse_string in JSONDecoder

Open
#74,178 14 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

3.7 (EOL) stdlib type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Description

BPO 29992
Nosy @rhettinger, @etrepum, @ezio-melotti, @methane, @serhiy-storchaka
Files
  • scanner.py: Modified JSON module's scanner.py
  • decoder.py: Modified JSON module's decoder.py
  • init.py: Modified JSON module's init.py
  • 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 = 'https://github.com/etrepum'
    closed_at = None
    created_at = <Date 2017-04-05.08:22:05.524>
    labels = ['3.7', 'type-feature', 'library']
    title = 'Expose parse_string in JSONDecoder'
    updated_at = <Date 2022-02-17.02:41:38.992>
    user = 'https://bugs.python.org/oberstet'
    

    bugs.python.org fields:

    activity = <Date 2022-02-17.02:41:38.992>
    actor = 'methane'
    assignee = 'bob.ippolito'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2017-04-05.08:22:05.524>
    creator = 'oberstet'
    dependencies = []
    files = ['47374', '47375', '47376']
    hgrepos = []
    issue_num = 29992
    keywords = []
    message_count = 14.0
    messages = ['291167', '291172', '291173', '291180', '291186', '292707', '292782', '309763', '309765', '309766', '309819', '309820', '413338', '413378']
    nosy_count = 8.0
    nosy_names = ['rhettinger', 'bob.ippolito', 'ezio.melotti', 'methane', 'oberstet', 'serhiy.storchaka', 'Levi Cameron', 'Adri\xc3\xa1n Orive']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue29992'
    versions = ['Python 3.7']
    

    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.

    Assessment

    This issue has not been assessed yet.

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.