Message286430
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. |
|
Date |
User |
Action |
Args |
2017-01-29 05:55:23 | martin.panter | set | recipients:
+ martin.panter, lemburg, georg.brandl, larry, benjamin.peterson |
2017-01-29 05:55:23 | martin.panter | set | messageid: <1485669323.78.0.620846597719.issue23980@psf.upfronthosting.co.za> |
2017-01-29 05:55:23 | martin.panter | link | issue23980 messages |
2017-01-29 05:55:23 | martin.panter | create | |
|