socket.getfqdn() doesn't cope properly with purely DNS-based setups

Ouverte
#49,254 24 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

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

Piste de recherche

Start at the socket.getfqdn() entry point and compare its behavior in purely DNS-based setups with the outputs documented by python5004-test.c. Review python2.7-socket-getfqdn.patch, including the updated python2.7-socket-getfqdn.patch, and use the observed discrepancy to define the expected behavior and tests for the Library (Lib) component.

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

Description

3.10 3.11 3.9 (EOL) stdlib topic-socket type-bug
BPO 5004
Nosy @loewis, @tiran, @mcepl, @bitdancer, @thomaswaldmann, @jan-hudec, @shoop
Files
  • python2.7-socket-getfqdn.patch
  • python5004-test.c: test C program showing various gethost function output on my system
  • python2.7-socket-getfqdn.patch: Updated patch, originally by Stijn.Hoop
  • 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 2009-01-19.22:29:02.219>
    labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
    title = "socket.getfqdn() doesn't cope properly with purely DNS-based setups"
    updated_at = <Date 2021-12-16.17:35:04.319>
    user = 'https://bugs.python.org/dfranke'
    

    bugs.python.org fields:

    activity = <Date 2021-12-16.17:35:04.319>
    actor = 'mcepl'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2009-01-19.22:29:02.219>
    creator = 'dfranke'
    dependencies = []
    files = ['29919', '29921', '50390']
    hgrepos = []
    issue_num = 5004
    keywords = ['patch']
    message_count = 24.0
    messages = ['80216', '109635', '109647', '162508', '173987', '187065', '187098', '187234', '187237', '187238', '187253', '187256', '187350', '187355', '297435', '300593', '308979', '372583', '404775', '404780', '404796', '404806', '404826', '405364']
    nosy_count = 14.0
    nosy_names = ['loewis', 'christian.heimes', 'mcepl', 'r.david.murray', 'dfranke', 'devurandom', 'mcjeff', 'ankitoshniwal', 'Thomas.Waldmann', 'Stijn.Hoop', 'bulb', 'James Shewey', 'richard.security.consultant', 'shoop']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue5004'
    versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
    

    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.