Difficult or impossible to figure out how garbage collector and weak references should interact for user-defined extension types

Open
#60,399 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing the issue description and its Documentation component, then inspect the relevant Python documentation for garbage collection, weak references, and user-defined extension types. No file, test, or entry point is named in the issue, so first identify the documentation location and the specific guidance that is missing. Done means the interaction is documented clearly enough for users of extension types to determine the correct behavior.

Written by the indexing model from the issue text.

Description

docs type-bug
BPO 16195
Nosy @jcea, @pitrou, @scoder, @asvetlov, @phmc

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 2012-10-11.13:10:21.354>
labels = ['type-bug', 'docs']
title = 'Difficult or impossible to figure out how garbage collector and weak references should interact for user-defined extension types'
updated_at = <Date 2013-10-05.09:56:16.835>
user = 'https://bugs.python.org/exarkun'

bugs.python.org fields:

activity = <Date 2013-10-05.09:56:16.835>
actor = 'scoder'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2012-10-11.13:10:21.354>
creator = 'exarkun'
dependencies = []
files = []
hgrepos = []
issue_num = 16195
keywords = []
message_count = 3.0
messages = ['172639', '172641', '198983']
nosy_count = 7.0
nosy_names = ['jcea', 'exarkun', 'pitrou', 'scoder', 'asvetlov', 'docs@python', 'pconnell']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue16195'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3', '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.