Incorrect operand precedence when implementing sequences in C

Open
#55,686 29 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
c, python
Domain
compilers

Research direction

Start by reviewing the historical patches issue11477_LHS_prededence.diff, 650549138a3d.diff, and 8bd713a823b5.diff, then read the linked issue discussion to identify the affected interpreter-core code. Establish the current C implementation and regression coverage for sequence operand precedence; done means the incorrect precedence is corrected and relevant tests pass.

Written by the indexing model from the issue text.

Description

3.11 interpreter-core type-bug
BPO 11477
Nosy @rhettinger, @terryjreedy, @gpshead, @ncoghlan, @cfbolz, @benjaminp, @merwok, @alex, @Trundle, @meadori, @durban, @ericsnowcurrently, @serhiy-storchaka, @iritkatriel
Files
  • issue11477_LHS_prededence.diff: Patch generated via rdiff extension
  • 650549138a3d.diff
  • 8bd713a823b5.diff
    		•

    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 2011-03-12.21:24:50.923>
labels = ['interpreter-core', 'type-bug', '3.11']
title = 'Incorrect operand precedence when implementing sequences in C'
updated_at = <Date 2021-10-26.00:55:14.406>
user = 'https://github.com/terryjreedy'

    bugs.python.org fields:

    activity = <Date 2021-10-26.00:55:14.406>
actor = 'gregory.p.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2011-03-12.21:24:50.923>
creator = 'terry.reedy'
dependencies = []
files = ['21219', '21368', '21386']
hgrepos = ['3']
issue_num = 11477
keywords = ['patch']
message_count = 27.0
messages = ['130698', '130728', '130736', '130812', '130866', '130867', '130909', '130925', '130974', '130976', '130994', '131001', '131004', '131007', '131022', '131030', '131057', '131211', '131212', '132052', '158917', '158918', '160138', '179031', '243301', '405003', '405017']
nosy_count = 14.0
nosy_names = ['rhettinger', 'terry.reedy', 'gregory.p.smith', 'ncoghlan', 'Carl.Friedrich.Bolz', 'benjamin.peterson', 'eric.araujo', 'alex', 'Trundle', 'meador.inge', 'daniel.urban', 'eric.snow', 'serhiy.storchaka', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11477'
versions = ['Python 3.11']

    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.