Determining the failure of C API call is ambiguous

Open
#70,963 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, python
Domain
backend

Research direction

Start by reviewing the linked check_error_occurred.patch and the original BPO issue 26776. Investigate how the affected C API call reports failure and determine what behavior the patch proposes. Done means the failure result is no longer ambiguous, with the relevant interpreter-core behavior covered by the project’s existing checks.

Written by the indexing model from the issue text.

Description

interpreter-core topic-C-API
BPO 26776
Nosy @vstinner, @serhiy-storchaka
Files
  • check_error_occurred.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 2016-04-16.08:02:38.488>
labels = ['interpreter-core']
title = 'Determining the failure of C API call is ambiguous'
updated_at = <Date 2016-04-16.09:27:24.259>
user = 'https://github.com/serhiy-storchaka'

    bugs.python.org fields:

    activity = <Date 2016-04-16.09:27:24.259>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2016-04-16.08:02:38.488>
creator = 'serhiy.storchaka'
dependencies = []
files = ['42478']
hgrepos = []
issue_num = 26776
keywords = ['patch']
message_count = 2.0
messages = ['263540', '263544']
nosy_count = 2.0
nosy_names = ['vstinner', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue26776'
versions = []

    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.