Concrete object C API considered harmful to subclasses of builtin types

Offen
#55,186 32 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
25/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
documentation

Rechercherichtung

Start by reading the linked issue10977_list.patch, which is identified as a patch for list, then inspect the relevant Python C API documentation. Determine which documentation still needs clarification about concrete object APIs and subclasses of builtin types. Done means the affected documentation clearly addresses the issue’s stated concern.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

docs topic-C-API type-bug
BPO 10977
Nosy @rhettinger, @ncoghlan, @pitrou, @scoder, @benjaminp, @merwok, @Trundle, @meadori, @durban, @ericsnowcurrently, @MojoVampire
Files
  • issue10977_list.patch: Patch for list.
    		•

    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 2011-01-21.23:49:24.089>
labels = ['type-bug', 'docs']
title = 'Concrete object C API considered harmful to subclasses of builtin types'
updated_at = <Date 2015-05-13.21:37:51.271>
user = 'https://github.com/rhettinger'

    bugs.python.org fields:

    activity = <Date 2015-05-13.21:37:51.271>
actor = 'ppperry'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2011-01-21.23:49:24.089>
creator = 'rhettinger'
dependencies = []
files = ['21303']
hgrepos = []
issue_num = 10977
keywords = ['patch']
message_count = 31.0
messages = ['126800', '131489', '131494', '131537', '131538', '131550', '131551', '133026', '133027', '133032', '133126', '133130', '133132', '133137', '133138', '133139', '133141', '133176', '133191', '200741', '200752', '200804', '200837', '200842', '201205', '201247', '201248', '201249', '201250', '201256', '201260']
nosy_count = 13.0
nosy_names = ['rhettinger', 'ncoghlan', 'pitrou', 'scoder', 'benjamin.peterson', 'eric.araujo', 'Arfrever', 'Trundle', 'meador.inge', 'daniel.urban', 'docs@python', 'eric.snow', 'josh.r']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue10977'
versions = ['Python 3.3']

    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.