submodule of c-extension module is quirky

Open
#87,533 6 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
backend

Research direction

Start with test.c, the complete C module reproducer linked in the issue, and inspect linked PR gh-119152 for the current work. Use the reproducer to understand the quirky submodule behavior and verify that the behavior is corrected without losing the reported case.

Written by the indexing model from the issue text.

Description

interpreter-core
BPO 43367
Nosy @mattip, @skoslowski, @YannickJadoul
Files
  • test.c: Complete C module to reproduce the issue
    		•

    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 2021-03-02.11:41:23.575>
labels = []
title = 'submodule of c-extension module is quirky'
updated_at = <Date 2021-03-02.14:54:05.759>
user = 'https://github.com/mattip'

    bugs.python.org fields:

    activity = <Date 2021-03-02.14:54:05.759>
actor = 'skoslowski'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2021-03-02.11:41:23.575>
creator = 'mattip'
dependencies = []
files = ['49844']
hgrepos = []
issue_num = 43367
keywords = []
message_count = 2.0
messages = ['387917', '387935']
nosy_count = 3.0
nosy_names = ['mattip', 'skoslowski', 'YannickJadoul']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue43367'
versions = []

    Linked PRs
    • gh-119152
    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.