➜

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 JonFoster
Recipients JonFoster, georg.brandl
Date 2009-09-17.14:09:57
SpamBayes Score 3.2079342e-06
Marked as misclassified No
Message-id <1253196599.56.0.25129944047.issue6930@psf.upfronthosting.co.za>
In-reply-to
Content 
The documentation for the C API function PyUnicode_DecodeUTF16() does
not match the code.

If *byteorder is 1 or -1, the documentation says that the function looks
for a BOM.  It doesn't.  This patch updates the documentation to match
the code.

(Also, I just realised that the docs for PyUnicode_DecodeUTF32() have
the exact same bug.  That is NOT fixed by this patch).

This patch also clarifies the PyUnicode_EncodeUTF16() docs.
History
Date User Action Args
2009-09-17 14:09:59JonFostersetrecipients: + JonFoster, georg.brandl
2009-09-17 14:09:59JonFostersetmessageid: <1253196599.56.0.25129944047.issue6930@psf.upfronthosting.co.za>
2009-09-17 14:09:58JonFosterlinkissue6930 messages
2009-09-17 14:09:58JonFostercreate