Use code.co_qualname to provide richer information

Open
#90,810 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Review the issue references and PR python/cpython#31150 first, then trace the interpreter entry point that reports the current information and determine how code.co_qualname is intended to enrich it. The issue names no source files or tests; done means the relevant information is richer without changing unrelated behavior.

Written by the indexing model from the issue text.

Description

3.11 interpreter-core type-feature
BPO 46652
Nosy @aroberge, @pablogsal, @P403n1x87, @sweeneyde
PRs
  • python/cpython#31150
    		•

    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 2022-02-05.21:25:54.999>
labels = ['interpreter-core', 'type-feature', '3.11']
title = 'Use code.co_qualname to provide richer information'
updated_at = <Date 2022-02-06.10:04:22.148>
user = 'https://github.com/P403n1x87'

    bugs.python.org fields:

    activity = <Date 2022-02-06.10:04:22.148>
actor = 'Gabriele Tornetta'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2022-02-05.21:25:54.999>
creator = 'Gabriele Tornetta'
dependencies = []
files = []
hgrepos = []
issue_num = 46652
keywords = ['patch']
message_count = 3.0
messages = ['412598', '412616', '412622']
nosy_count = 4.0
nosy_names = ['aroberge', 'pablogsal', 'Gabriele Tornetta', 'Dennis Sweeney']
pr_nums = ['31150']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue46652'
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.