Popen should raise ValueError if pass a string when shell=False or a list when shell=True

Offen
#52,087 32 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
python

Rechercherichtung

Read the linked test_subprocess.py test case first, then locate the Popen behavior it exercises. Done means coverage verifies ValueError for a string with shell=False and for a list with shell=True, while preserving the existing subprocess tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

pending stdlib type-feature
BPO 7839
Nosy @csernazs, @ncoghlan, @vstinner, @larryhastings, @ericvsmith, @giampaolo, @merwok, @bitdancer, @briancurtin, @asvetlov
Files
  • test_subprocess.py: Test case for this bug, works in Python 2 and Python 3.
  • 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 2010-02-02.19:08:03.339>
    labels = ['type-feature', 'library']
    title = 'Popen should raise ValueError if pass a string when shell=False or a list when shell=True'
    updated_at = <Date 2013-11-06.19:37:27.696>
    user = 'https://github.com/bitdancer'
    

    bugs.python.org fields:

    activity = <Date 2013-11-06.19:37:27.696>
    actor = 'akuchling'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2010-02-02.19:08:03.339>
    creator = 'r.david.murray'
    dependencies = []
    files = ['17587']
    hgrepos = []
    issue_num = 7839
    keywords = []
    message_count = 31.0
    messages = ['98754', '100202', '100205', '100206', '100207', '100209', '107310', '107311', '107313', '107316', '107322', '107353', '107365', '107369', '107770', '111337', '157217', '157227', '157228', '157230', '157252', '157259', '157269', '157294', '157322', '157323', '157332', '157608', '157613', '157800', '160587']
    nosy_count = 15.0
    nosy_names = ['holdenweb', 'csernazs', 'ncoghlan', 'vstinner', 'dstanek', 'larry', 'eric.smith', 'giampaolo.rodola', 'eric.araujo', 'Arfrever', 'r.david.murray', 'brian.curtin', 'cvrebert', 'asvetlov', 'Alexander.Belopolsky']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue7839'
    versions = ['Python 3.3']
    

    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.