"universal newlines" subprocess support broken with select- and poll-based communicate()

Offen
#56,832 17 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
20/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python

Rechercherichtung

Start by reviewing issue12623_failing_test.diff and the select- and poll-based communicate() behavior described in the issue. Check superseding issue bpo-16903 before investigating further, since this issue has no linked pull request and its historical patch may be out of date. Done would require a current reproducer and passing subprocess tests for universal newlines.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

stdlib tests topic-subprocess type-bug
BPO 12623
Nosy @birkenfeld, @gpshead, @pitrou, @bitdancer, @asvetlov, @cjerdonek, @vadmium
Superseder
  • bpo-16903: subprocess.Popen.communicate with universal_newlines=True doesn't accept strings on 3.2
  • Files
  • issue12623_failing_test.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-07-23.20:11:32.674>
    labels = ['tests', 'type-bug', 'library']
    title = '"universal newlines" subprocess support broken with select- and poll-based communicate()'
    updated_at = <Date 2016-06-12.20:34:36.463>
    user = 'https://github.com/pitrou'
    

    bugs.python.org fields:

    activity = <Date 2016-06-12.20:34:36.463>
    actor = 'BreamoreBoy'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)', 'Tests']
    creation = <Date 2011-07-23.20:11:32.674>
    creator = 'pitrou'
    dependencies = []
    files = ['26837']
    hgrepos = []
    issue_num = 12623
    keywords = ['patch']
    message_count = 17.0
    messages = ['141014', '168317', '168320', '168322', '168325', '168328', '168329', '168330', '168331', '168333', '168335', '168336', '168340', '168557', '169046', '220743', '268346']
    nosy_count = 7.0
    nosy_names = ['georg.brandl', 'gregory.p.smith', 'pitrou', 'r.david.murray', 'asvetlov', 'chris.jerdonek', 'martin.panter']
    pr_nums = []
    priority = 'normal'
    resolution = 'out of date'
    stage = 'patch review'
    status = 'open'
    superseder = '16903'
    type = 'behavior'
    url = 'https://bugs.python.org/issue12623'
    versions = ['Python 3.4', 'Python 3.5']
    

    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.