Constructor signatures missing in types module documentation

Ouverte
#55,985 22 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
35/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
python
Domaine
documentation

Piste de recherche

Start by reviewing the existing issue11776-sigs-docs-first.diff and complete-patch-with-table-issue-11776.diff, then compare their proposed changes with the current types module documentation. Check the documented constructors and confirm that their signatures are complete and accurate. Done means the missing constructor signatures are documented and the documentation build or relevant checks pass.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

docs type-feature
BPO 11776
Nosy @birkenfeld, @terryjreedy, @ncoghlan, @ezio-melotti, @merwok, @ericsnowcurrently, @eamanu, @csabella, @tza0987
Files
  • issue11776-sigs-docs-first.diff
  • issue11776-first-easy-part-lambda-.diff
  • signatures-full-patch.diff
  • complete-patch-with-table-issue-11776.diff
  • 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-04-05.20:53:24.787>
    labels = ['easy', '3.8', 'type-feature', '3.7', 'docs']
    title = 'Constructor signatures missing in types module documentation'
    updated_at = <Date 2019-02-24.23:42:44.704>
    user = 'https://bugs.python.org/techtonik'
    

    bugs.python.org fields:

    activity = <Date 2019-02-24.23:42:44.704>
    actor = 'terry.reedy'
    assignee = 'docs@python'
    closed = False
    closed_date = None
    closer = None
    components = ['Documentation']
    creation = <Date 2011-04-05.20:53:24.787>
    creator = 'techtonik'
    dependencies = []
    files = ['26969', '26982', '27003', '27047']
    hgrepos = []
    issue_num = 11776
    keywords = ['patch', 'easy']
    message_count = 22.0
    messages = ['133089', '133352', '133354', '133365', '133366', '133374', '133376', '166149', '166152', '168864', '168866', '168901', '168933', '168947', '168992', '169156', '169158', '169159', '169397', '336475', '336478', '336491']
    nosy_count = 12.0
    nosy_names = ['georg.brandl', 'terry.reedy', 'ncoghlan', 'ezio.melotti', 'eric.araujo', 'docs@python', 'guandalino', 'eric.snow', 'mikehoy', 'eamanu', 'cheryl.sabella', 'Tza0987']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue11776'
    versions = ['Python 3.7', 'Python 3.8']
    

    Langage dominant
    Python
    Étoiles
    77.2k
    Forks
    36k
    Merge moyen
    1 j 9 h
    PR mergées (30 j)
    558

    Guide de contribution

    Ouvrir le guide de contribution

    Par où commencer

    1. Lisez l'issue en entier, puis le guide de contribution du projet.
    2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
    3. Forkez le dépôt et travaillez sur une branche.
    4. Ouvrez une pull request qui référence le numéro de l'issue.

    Autres issues de python/cpython

    Toutes les issues de python/cpython

    Recevez les nouvelles issues par e-mail

    Un résumé court des issues GitHub adaptées aux débutants.