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

Offen
#60,399 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
documentation

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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']

Vorherrschende Sprache
Python
Sterne
77.2k
Forks
36k
Ø Merge
1 T. 9 Std.
Gemergte PRs (30 T.)
558

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus python/cpython

Alle Issues in python/cpython

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.