Skip to content

[3.8] bpo-41672: Fix type mismatches in imaplib docs (GH-22207) #22218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 12, 2020
Merged

[3.8] bpo-41672: Fix type mismatches in imaplib docs (GH-22207) #22218

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Doc/library/imaplib.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,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``].


Expand Down Expand Up @@ -186,7 +186,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).

Expand Down