Not documented special names

Ouverte
#67,827 11 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
45/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
python
Domaine
documentation

Piste de recherche

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.

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

Description

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

    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

    Issues similaires

    Plus d'issues Python

    Recevez les nouvelles issues par e-mail

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