PEP447: Add type.__getdescriptor__

Open
#62,381 27 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the latest referenced proposal, pep447-2015-07-26.txt, alongside super-hook-proposal.rst and the earlier issue-18181 patches. The issue is in patch review with no repository entry point or tests named; done would require an agreed implementation of type.getdescriptor, not another proposal revision.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature
BPO 18181
Nosy @ronaldoussoren, @amauryfa
Files
  • supers_updated.py
  • issue-18181-poc-v4.txt
  • super-hook-proposal.rst
  • issue18181-locallookup-only-super.txt
  • issue-18181-full-v1.txt
  • issue-18181-full-v2.txt
  • issue-18181-full-v2b.txt
  • issue-18181-full-v3.txt
  • issue-18181-full-v4.txt
  • pep447-2015-07-25.txt
  • pep447-micro-bench.py
  • pep447-2015-07-25-v2.txt
  • pep447-2015-07-26.txt
  • pep447-2015-07-26.txt: Updated patch for trunk with minor code cleanup
  • 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-06-10.13:15:53.900>
    labels = ['interpreter-core', 'type-bug']
    title = 'PEP447: Add type.__getdescriptor__'
    updated_at = <Date 2016-07-24.07:56:54.166>
    user = 'https://github.com/ronaldoussoren'
    

    bugs.python.org fields:

    activity = <Date 2016-07-24.07:56:54.166>
    actor = 'ronaldoussoren'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2013-06-10.13:15:53.900>
    creator = 'ronaldoussoren'
    dependencies = []
    files = ['30547', '30766', '30767', '30928', '30951', '31008', '31014', '31071', '31107', '40012', '40013', '40017', '40027', '43853']
    hgrepos = []
    issue_num = 18181
    keywords = ['patch']
    message_count = 27.0
    messages = ['190905', '190909', '190912', '190920', '190921', '190965', '190971', '190972', '190976', '190979', '191020', '191021', '192274', '192275', '193100', '193109', '193232', '193538', '193547', '193861', '194038', '247187', '247323', '247330', '247349', '247350', '247419']
    nosy_count = 2.0
    nosy_names = ['ronaldoussoren', 'amaury.forgeotdarc']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue18181'
    versions = ['Python 3.6']
    

    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.