Deprecate the frame hack for implicitly getting module details

Open
#62,163 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start with the linked BPO-17963 discussion and its dependency BPO-17941; the issue names no repository files, tests, or entry points. Establish the intended replacement and scope for deprecating implicit module details, then define the tests and documentation needed to verify the change.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 17963
Nosy @gvanrossum, @brettcannon, @rhettinger, @ncoghlan, @vstinner, @ericsnowcurrently
Dependencies
  • bpo-17941: namedtuple should support fully qualified name for more portable pickling
  • 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 2013-05-12.13:09:13.550>
    labels = ['type-feature']
    title = 'Deprecate the frame hack for implicitly getting module details'
    updated_at = <Date 2015-07-21.07:34:48.995>
    user = 'https://github.com/ncoghlan'
    

    bugs.python.org fields:

    activity = <Date 2015-07-21.07:34:48.995>
    actor = 'ethan.furman'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = []
    creation = <Date 2013-05-12.13:09:13.550>
    creator = 'ncoghlan'
    dependencies = ['17941']
    files = []
    hgrepos = []
    issue_num = 17963
    keywords = []
    message_count = 9.0
    messages = ['189028', '189033', '189034', '189035', '189044', '189163', '194319', '236563', '236572']
    nosy_count = 7.0
    nosy_names = ['gvanrossum', 'brett.cannon', 'rhettinger', 'ncoghlan', 'vstinner', 'eli.bendersky', 'eric.snow']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue17963'
    versions = ['Python 3.4']
    

    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.