Author gregory.p.smith
Recipients docs@python, gregory.p.smith
Date 2015-10-19.06:42:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445236924.11.0.92849861938.issue25438@psf.upfronthosting.co.za>
In-reply-to
Content
https://docs.python.org/3/c-api/structures.html#c.PyMemberDef

T_STRING members are turned into str objects in Python.  The documentation needs updating to mention which codec the char * bytes are treated as.

Solving this issue involves code inspection and leaving pointers to that code here in the issue, then updating the docs to mention the requirements for the char * member data as well as what happens upon assignment for non-READONLY T_STRING data (a different restriction?  or encoding to the same codec?)

My _guess_ would be UTF-8 or ASCII but I'll let someone else dive in and find out.  This is a Python 3 specific documentation clarification.
History
Date User Action Args
2015-10-19 06:42:04gregory.p.smithsetrecipients: + gregory.p.smith, docs@python
2015-10-19 06:42:04gregory.p.smithsetmessageid: <1445236924.11.0.92849861938.issue25438@psf.upfronthosting.co.za>
2015-10-19 06:42:03gregory.p.smithlinkissue25438 messages
2015-10-19 06:42:03gregory.p.smithcreate