This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author dkg
Recipients barry, dkg, r.david.murray
Date 2020-01-24.20:24:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579897476.32.0.1859965096.issue39447@roundup.psfhosted.org>
In-reply-to
Content
The imaplib documentation says:


> 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
> tuple. If a tuple, then the first part is the header of the response, 
> and the second part contains the data (ie: ‘literal’ value).

However, "Each data is either a string, or a tuple" does not appear to be correct.   If the element of data is not a tuple, it appears to be a bytes object, not a string (because it is dealing with network streams of bytes internally)

This is probably old documentation left over from python 2, when strings and bytes were the same.
History
Date User Action Args
2020-01-24 20:24:36dkgsetrecipients: + dkg, barry, r.david.murray
2020-01-24 20:24:36dkgsetmessageid: <1579897476.32.0.1859965096.issue39447@roundup.psfhosted.org>
2020-01-24 20:24:36dkglinkissue39447 messages
2020-01-24 20:24:36dkgcreate