fnmatch, glob: Allow curly brace expansion

Offen
#53,793 55 Kommentare 2 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
25/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
backend

Rechercherichtung

Start by reviewing the existing fnmatch and glob entry points, then compare the proposed behavior in python/cpython#6299 and the uploaded 0001-Curly-brace-expansion-in-glob.patch. Done means curly brace expansion is supported for fnmatch and glob, with the related unused-import cleanup from 0002-Remove-unused-import.patch addressed.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

stdlib type-feature
BPO 9584
Nosy @freddrake, @ronaldoussoren, @pitrou, @ericvsmith, @tjguk, @ezio-melotti, @merwok, @stevendaprano, @bitdancer, @bochecha, @Julian, @serhiy-storchaka, @csabella, @matusvalo
PRs
  • python/cpython#6299
    		•
    Files
  • 0001-Curly-brace-expansion-in-glob.patch: Curly brace expansion in glob
  • 0002-Remove-unused-import.patch
    		•

    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-08-13.08:36:51.246>
labels = ['type-feature', 'library']
title = 'fnmatch, glob: Allow curly brace expansion'
updated_at = <Date 2019-05-14.12:56:15.952>
user = 'https://github.com/bochecha'

    bugs.python.org fields:

    activity = <Date 2019-05-14.12:56:15.952>
actor = 'cheryl.sabella'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2010-08-13.08:36:51.246>
creator = 'bochecha'
dependencies = []
files = ['21001', '21002']
hgrepos = []
issue_num = 9584
keywords = ['patch']
message_count = 55.0
messages = ['113750', '113751', '113753', '113756', '113758', '113762', '113765', '113766', '113767', '113773', '113787', '113789', '113888', '113897', '114115', '114119', '120082', '122614', '124422', '124423', '124459', '124461', '124462', '130098', '130099', '130506', '131613', '131622', '135558', '135587', '135588', '174712', '174879', '174880', '174882', '174883', '174916', '174919', '174938', '174963', '174974', '174978', '174980', '174984', '174991', '174995', '174996', '174997', '175001', '175190', '175193', '175217', '314633', '335173', '342458']
nosy_count = 18.0
nosy_names = ['fdrake', 'ronaldoussoren', 'pitrou', 'eric.smith', 'tim.golden', 'kveretennicov', 'ezio.melotti', 'eric.araujo', 'Arfrever', 'steven.daprano', 'r.david.murray', 'bochecha', 'Julian', 'python-dev', 'serhiy.storchaka', 'ysangkok', 'cheryl.sabella', 'Mat\xc3\xba\xc5\xa1 Valo']
pr_nums = ['6299']
priority = 'low'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue9584'
versions = ['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.