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 martin.panter
Recipients benjamin.peterson, georg.brandl, larry, lemburg, martin.panter
Date 2017-01-29.05:55:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485669323.78.0.620846597719.issue23980@psf.upfronthosting.co.za>
In-reply-to
Content
The O! and O& units are in a similar situation. They just use a different font and descriptive name, rather than a specific type:

``O!`` (object) [*typeobject*, PyObject \*]
``O&`` (object) [*converter*, *anything*]

Following this lead, you could write:

``es`` (:class:`str`) [*encoding*, char \*buffer]
``et`` (. . .) [*encoding*, char \*buffer]
``es#`` (:class:`str`) [*encoding*, char \*buffer, int buffer_length]
``et#`` (. . .) [*encoding*, char \*buffer, int buffer_length]

The text description should explain what *encoding* is, but it appears it may already do that well enough.
History
Date User Action Args
2017-01-29 05:55:23martin.pantersetrecipients: + martin.panter, lemburg, georg.brandl, larry, benjamin.peterson
2017-01-29 05:55:23martin.pantersetmessageid: <1485669323.78.0.620846597719.issue23980@psf.upfronthosting.co.za>
2017-01-29 05:55:23martin.panterlinkissue23980 messages
2017-01-29 05:55:23martin.pantercreate