From: Norbert Cyran Date: Sat, 12 Sep 2020 07:58:56 +0000 (+0200) Subject: bpo-41672: Fix type mismatches in imaplib docs (GH-22207) X-Git-Tag: v3.10.0a1~128 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c75330605d4795850ec74fdc4d69aa5d92f76c00;p=thirdparty%2FPython%2Fcpython.git bpo-41672: Fix type mismatches in imaplib docs (GH-22207) --- diff --git a/Doc/library/imaplib.rst b/Doc/library/imaplib.rst index 7c5b07501615..02ecfd95d437 100644 --- a/Doc/library/imaplib.rst +++ b/Doc/library/imaplib.rst @@ -143,7 +143,7 @@ The following utility functions are defined: .. function:: Int2AP(num) - Converts an integer into a string representation using characters from the set + Converts an integer into a bytes representation using characters from the set [``A`` .. ``P``]. @@ -197,7 +197,7 @@ you want to avoid having an argument string quoted (eg: the *flags* argument to Each command returns a tuple: ``(type, [data, ...])`` where *type* is usually ``'OK'`` or ``'NO'``, and *data* is either the text from the command response, -or mandated results from the command. Each *data* is either a string, or a +or mandated results from the command. Each *data* is either a ``bytes``, or a tuple. If a tuple, then the first part is the header of the response, and the second part contains the data (ie: 'literal' value).