python / python/cpython

json.dumps to check for obj.__json__ before raising TypeError

Open
#71,549 12 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

stdlib type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 27362
Nosy @rhettinger, @etrepum, @stevendaprano, @bitdancer, @berkerpeksag, @serhiy-storchaka, @Vgr255
Files
  • json-customize.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 = 'https://github.com/etrepum'
    closed_at = None
    created_at = <Date 2016-06-21.13:09:18.565>
    labels = ['3.7', 'type-feature', 'library']
    title = 'json.dumps to check for obj.__json__ before raising TypeError'
    updated_at = <Date 2018-02-01.16:33:45.801>
    user = 'https://bugs.python.org/DanielWard'
    

    bugs.python.org fields:

    activity = <Date 2018-02-01.16:33:45.801>
    actor = 'ulope'
    assignee = 'bob.ippolito'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2016-06-21.13:09:18.565>
    creator = 'Daniel Ward'
    dependencies = []
    files = ['46701']
    hgrepos = []
    issue_num = 27362
    keywords = ['patch']
    message_count = 11.0
    messages = ['268991', '268993', '268995', '268999', '269002', '269003', '269021', '269091', '289001', '289006', '289007']
    nosy_count = 10.0
    nosy_names = ['rhettinger', 'bob.ippolito', 'steven.daprano', 'r.david.murray', 'berker.peksag', 'serhiy.storchaka', 'abarry', 'ulope', 'Daniel Ward', 'Ollie Ford']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue27362'
    versions = ['Python 3.7']
    

    Linked PRs
    • gh-153607

    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.