email parsing docs: clarify that only ASCII strings are supported

Open
#69,731 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
32/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reading the issue discussion and the attached email_get_payload__test.py and parse-text.py files to understand the reported behavior. Locate the current email parsing documentation and confirm where string input is described. Done means the relevant documentation clearly states that only ASCII strings are supported, with any existing documentation checks still passing.

Written by the indexing model from the issue text.

Description

docs stdlib topic-email
BPO 25545
Nosy @warsaw, @jaraco, @bitdancer, @jayvdb
Files
  • email_get_payload__test.py
  • parse-text.py
    		•

    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 2015-11-03.14:43:30.136>
labels = ['type-bug', 'library']
title = 'email parsing docs: clarify that only ASCII strings are supported'
updated_at = <Date 2019-04-26.16:47:53.820>
user = 'https://bugs.python.org/tanzerswingcoat'

    bugs.python.org fields:

    activity = <Date 2019-04-26.16:47:53.820>
actor = 'immerrr again'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-11-03.14:43:30.136>
creator = 'tanzer@swing.co.at'
dependencies = []
files = ['40934', '47978']
hgrepos = []
issue_num = 25545
keywords = []
message_count = 19.0
messages = ['253994', '254014', '254041', '254058', '254066', '254067', '254095', '254131', '254179', '254189', '254262', '254315', '254322', '254325', '331159', '331183', '340841', '340931', '340934']
nosy_count = 6.0
nosy_names = ['barry', 'jaraco', 'r.david.murray', 'jayvdb', 'tanzer@swing.co.at', 'immerrr again']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25545'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.