No-argument super in method with variable arguments raises SystemError

Open
#59,958 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reviewing the historical issue15753_varargsuper.patch linked in the issue and the CPython Interpreter Core area. Reproduce the no-argument super failure in a method with variable arguments, then add coverage and confirm that the case no longer raises SystemError.

Written by the indexing model from the issue text.

Description

3.8 (EOL) interpreter-core type-bug
BPO 15753
Nosy @amauryfa, @benjaminp, @ezio-melotti, @merwok, @bitdancer, @asvetlov, @vadmium, @MojoVampire, @remilapeyre
Files
  • issue15753_varargsuper.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 2012-08-21.11:52:40.230>
    labels = ['interpreter-core', 'type-bug', '3.8']
    title = 'No-argument super in method with variable arguments raises SystemError'
    updated_at = <Date 2019-02-14.10:09:42.758>
    user = 'https://bugs.python.org/jamessanders'
    

    bugs.python.org fields:

    activity = <Date 2019-02-14.10:09:42.758>
    actor = 'BreamoreBoy'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2012-08-21.11:52:40.230>
    creator = 'james.sanders'
    dependencies = []
    files = ['26976']
    hgrepos = []
    issue_num = 15753
    keywords = ['patch']
    message_count = 12.0
    messages = ['168757', '168959', '168989', '168995', '168997', '169002', '169720', '236499', '236554', '245571', '245578', '335472']
    nosy_count = 12.0
    nosy_names = ['amaury.forgeotdarc', 'benjamin.peterson', 'ezio.melotti', 'eric.araujo', 'Arfrever', 'r.david.murray', 'asvetlov', 'martin.panter', 'james.sanders', 'josh.r', 'Crist\xc3\xb3bal Ganter', 'remi.lapeyre']
    pr_nums = []
    priority = 'low'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue15753'
    versions = ['Python 3.8']
    

    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.