Charset.header_encode in email.charset doesn't take a maxlinelen argument and has inconsistent behavior with different encodings

Offen
#64,946 10 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
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
python
Bereich
backend

Rechercherichtung

Start at the email.charset.Charset.header_encode entry point and review the issue's BPO context for the reported maxlinelen and encoding differences. The payload names no files or tests, so identify the relevant email library tests and define completion as accepting maxlinelen while producing consistent behavior across encodings.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

stdlib topic-email type-bug
BPO 20747
Nosy @warsaw, @bitdancer, @ZackerySpytz

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 2014-02-23.17:59:37.009>
labels = ['type-bug', 'library', 'expert-email']
title = "Charset.header_encode in email.charset doesn't take a maxlinelen argument and has inconsistent behavior with different encodings"
updated_at = <Date 2020-08-31.09:59:28.543>
user = 'https://bugs.python.org/rednaw'

bugs.python.org fields:

activity = <Date 2020-08-31.09:59:28.543>
actor = 'ZackerySpytz'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2014-02-23.17:59:37.009>
creator = 'rednaw'
dependencies = []
files = []
hgrepos = []
issue_num = 20747
keywords = []
message_count = 10.0
messages = ['212011', '212045', '212072', '212093', '212098', '212101', '212107', '212111', '212112', '376145']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'rednaw', 'ZackerySpytz']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue20747'
versions = ['Python 2.7']

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.