email module should have a way to prepend and insert headers
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 45/100
Rechercherichtung
Start with Python's email module and review the linked suryak.patch, which proposes insert_header() to insert a header at the beginning. Check the existing header-manipulation behavior and discussion history first; the work is done when the module provides the requested prepend and insert capabilities with behavior consistent with its current API.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
| BPO | 18139 |
|---|---|
| Nosy | @warsaw, @bitdancer |
| Files |
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-06-05.04:35:54.493>
labels = ['type-feature', 'library', 'expert-email']
title = 'email module should have a way to prepend and insert headers'
updated_at = <Date 2016-08-22.15:32:58.051>
user = 'https://bugs.python.org/kbandla'
bugs.python.org fields:
activity = <Date 2016-08-22.15:32:58.051>
actor = 'barry'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2013-06-05.04:35:54.493>
creator = 'kbandla'
dependencies = []
files = ['34278']
hgrepos = []
issue_num = 18139
keywords = ['patch']
message_count = 10.0
messages = ['190641', '190658', '190661', '190662', '212642', '212645', '212646', '212731', '273380', '273381']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'kbandla', 'suryak']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue18139'
versions = ['Python 3.6']
- Vorherrschende Sprache
- Python
- Sterne
- 77.2k
- Forks
- 36k
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 558
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus python/cpython
-
docs pending
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
stdlib type-feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
stdlib type-feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
build type-bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
-
stdlib topic-email type-feature
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100