calendar should understand full- vs. half-width characters

Offen
#61,250 4 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
35/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python

Rechercherichtung

Start by reading Python's calendar module and the referenced dependency, bpo-12568, which concerns character width in columns. Determine the expected handling of full- and half-width characters and identify the relevant tests or entry points; done means the behavior is specified and covered by tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

stdlib type-feature
BPO 17048
Nosy @rhettinger, @terryjreedy, @ezio-melotti, @chason, @ishigoya
Dependencies
  • bpo-12568: Add functions to get the width in columns of a character
  • 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 2013-01-27.08:38:10.091>
    labels = ['type-feature', 'library']
    title = 'calendar should understand full- vs. half-width characters'
    updated_at = <Date 2018-01-29.05:13:25.560>
    user = 'https://bugs.python.org/nneonneo'
    

    bugs.python.org fields:

    activity = <Date 2018-01-29.05:13:25.560>
    actor = 'chason.chaffin'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2013-01-27.08:38:10.091>
    creator = 'nneonneo'
    dependencies = ['12568']
    files = []
    hgrepos = []
    issue_num = 17048
    keywords = []
    message_count = 4.0
    messages = ['180748', '180751', '181154', '311001']
    nosy_count = 6.0
    nosy_names = ['rhettinger', 'terry.reedy', 'nneonneo', 'ezio.melotti', 'chason.chaffin', 'ishigoya']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'needs patch'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue17048'
    versions = ['Python 3.4']
    

    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.