Not documented special names

Offen
#67,827 11 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
documentation

Rechercherichtung

Start by reviewing index-special.patch, described as indexing existing documentation, and compare it with the four listed documentation dependencies: self, sizeof, getinitargs, and base. Check the linked issue context and determine whether the special names are now documented; done means the relevant existing documentation is indexed or clarified without leaving those dependencies unresolved.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

docs type-feature
BPO 23639
Nosy @birkenfeld, @rhettinger, @terryjreedy, @ezio-melotti, @merwok, @vadmium, @serhiy-storchaka, @IanLee1521
Dependencies
  • bpo-14003: self on built-in functions is not as documented
  • bpo-15436: sizeof is not documented
  • bpo-22392: Clarify documentation of getinitargs
  • bpo-22456: base undocumented
    		•
    Files
  • index-special.patch: Index existing documentation
    		•

    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 2015-03-11.11:15:01.029>
labels = ['type-feature', 'docs']
title = 'Not documented special names'
updated_at = <Date 2015-09-02.18:13:56.514>
user = 'https://github.com/serhiy-storchaka'

    bugs.python.org fields:

    activity = <Date 2015-09-02.18:13:56.514>
actor = 'serhiy.storchaka'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation']
creation = <Date 2015-03-11.11:15:01.029>
creator = 'serhiy.storchaka'
dependencies = ['14003', '15436', '22392', '22456']
files = ['39793']
hgrepos = []
issue_num = 23639
keywords = ['patch']
message_count = 7.0
messages = ['237859', '237860', '237886', '238005', '238063', '245716', '249385']
nosy_count = 10.0
nosy_names = ['georg.brandl', 'rhettinger', 'terry.reedy', 'peter.otten', 'ezio.melotti', 'eric.araujo', 'docs@python', 'martin.panter', 'serhiy.storchaka', 'IanLee1521']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23639'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6']

    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.