There ought to be a way for extension types to associate documentation with their tp_new or tp_init methods

Open

#50,380 opened on May 27, 2009 2 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

The issue names the interpreter-core entry points tp_new and tp_init but no source file or test. Start by locating how extension types currently expose documentation for these methods, then find the relevant interpreter-core tests. Done means the issue's requested association mechanism is specified and covered for both entry points.

Written by the indexing model from the issue text.

Description

interpreter-core type-feature

BPO	6130
Nosy	@ncoghlan, @larryhastings, @ezio-melotti

^{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 2009-05-27.21:02:38.548>
labels = ['interpreter-core', 'type-feature']
title = 'There ought to be a way for extension types to associate documentation with their tp_new or tp_init methods'
updated_at = <Date 2014-06-27.11:55:56.390>
user = 'https://bugs.python.org/exarkun'

bugs.python.org fields:

activity = <Date 2014-06-27.11:55:56.390>
actor = 'ezio.melotti'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2009-05-27.21:02:38.548>
creator = 'exarkun'
dependencies = []
files = []
hgrepos = []
issue_num = 6130
keywords = []
message_count = 2.0
messages = ['88446', '112285']
nosy_count = 4.0
nosy_names = ['exarkun', 'ncoghlan', 'larry', 'ezio.melotti']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue6130'
versions = ['Python 3.5']

Dominant language: Python
Stars: 77.2k
Forks: 36k
Avg merge: 1d 9h
Merged PRs (30d): 558

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[bug] clean-merge parity integration fixtures fail the current approval gate Open

from:qa priority:P2 reliability tech-debt

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

spec-kitty/spec-kitty#4874 · Opened Sep 21, 2026
Update contributor page in the docs Open

fix: inaccuracy ⚠️

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

uabrc/uabrc.github.io#1255 · 1 comment · Opened Sep 21, 2026
[Task SDK] `BaseOperator.post_execute` is invoked without the `result` argument in the new task runner Open

kind:bug needs-triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

apache/airflow#73471 · 1 comment · Opened Sep 21, 2026
Use name macOS not darwin in release table Open

docs

Difficulty 1/5 Under an hour Newbie friendliness 85/100

visit-dav/visit#21164 · Opened Sep 21, 2026
melange/apko: attest-build-provenance always fails on fork PRs (missing id-token) Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

ethereum-optimism/factory#64 · Opened Sep 21, 2026

More Python issues