Different documentation for identical methods

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

Rechercherichtung

Start by reading the linked BPO issue 17858 and comparing the four uploaded patches: issue17858.patch through Patch 4. Identify which identical methods require different documentation and confirm the intended wording from the issue discussion. Done means the documentation discrepancy is resolved and the relevant documentation tests or checks pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

docs type-feature
BPO 17858
Nosy @birkenfeld, @bitdancer
Files
  • issue17858.patch: patch for issue 17858
  • issue17858.patch: Issue 17858 Patch 2
  • issue17858.patch: Issue 17858 Patch 3
  • issue17858.patch: issue 17858 Patch 4
  • 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 2013-04-27.22:58:04.996>
    labels = ['type-feature', 'docs']
    title = 'Different documentation for identical methods'
    updated_at = <Date 2013-05-09.15:19:20.670>
    user = 'https://bugs.python.org/amysyk'
    

    bugs.python.org fields:

    activity = <Date 2013-05-09.15:19:20.670>
    actor = 'amysyk'
    assignee = 'docs@python'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation']
    creation = <Date 2013-04-27.22:58:04.996>
    creator = 'amysyk'
    dependencies = []
    files = ['30039', '30047', '30136', '30184']
    hgrepos = []
    issue_num = 17858
    keywords = ['patch']
    message_count = 9.0
    messages = ['187945', '187946', '187947', '187948', '187965', '188004', '188450', '188717', '188781']
    nosy_count = 4.0
    nosy_names = ['georg.brandl', 'r.david.murray', 'docs@python', 'amysyk']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue17858'
    versions = ['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

    Neue Issues direkt in Ihr Postfach

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