Print information about an unexpectedly pending error before crashing

Open
#79,892 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files or tests; begin by reviewing the existing discussion and referenced PR #11513. Confirm the intended interpreter-core behavior and verify that an unexpected pending error is reported before the crash.

Written by the indexing model from the issue text.

Description

3.8 (EOL) interpreter-core type-feature
BPO 35711
Nosy @gpshead, @vstinner, @serhiy-storchaka, @sfreilich
PRs
  • python/cpython#11513
  • python/cpython#11513
  • python/cpython#11513
  • 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/gpshead'
    closed_at = None
    created_at = <Date 2019-01-10.20:57:59.719>
    labels = ['interpreter-core', 'type-feature', '3.8']
    title = 'Print information about an unexpectedly pending error before crashing'
    updated_at = <Date 2019-01-23.17:17:27.828>
    user = 'https://github.com/sfreilich'
    

    bugs.python.org fields:

    activity = <Date 2019-01-23.17:17:27.828>
    actor = 'vstinner'
    assignee = 'gregory.p.smith'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2019-01-10.20:57:59.719>
    creator = 'sfreilich'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 35711
    keywords = ['patch', 'patch', 'patch']
    message_count = 8.0
    messages = ['333418', '333442', '333450', '333451', '333687', '334025', '334054', '334265']
    nosy_count = 4.0
    nosy_names = ['gregory.p.smith', 'vstinner', 'serhiy.storchaka', 'sfreilich']
    pr_nums = ['11513', '11513', '11513']
    priority = 'normal'
    resolution = None
    stage = 'resolved'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue35711'
    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.