email.parser stops parsing headers too soon when given a defective message.
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
Start with the email.parser implementation and the attached continue-header.patch, then reproduce the behavior with a defective message. Trace where header parsing stops and compare the result with the patch's intended change. Done means defective messages continue parsing headers correctly without regressing normal parsing.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
| BPO | 26686 |
|---|---|
| Nosy | @warsaw, @msapiro, @bitdancer, @vadmium |
| 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 2016-04-01.17:46:30.047>
labels = ['type-bug', 'library', 'expert-email']
title = 'email.parser stops parsing headers too soon when given a defective message.'
updated_at = <Date 2016-08-10.22:57:36.138>
user = 'https://github.com/msapiro'
bugs.python.org fields:
activity = <Date 2016-08-10.22:57:36.138>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2016-04-01.17:46:30.047>
creator = 'msapiro'
dependencies = []
files = ['43374']
hgrepos = []
issue_num = 26686
keywords = ['patch']
message_count = 7.0
messages = ['262750', '262751', '262776', '268438', '272295', '272332', '272381']
nosy_count = 4.0
nosy_names = ['barry', 'msapiro', 'r.david.murray', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26686'
versions = ['Python 2.7', 'Python 3.5', '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