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 mkleehammer
Recipients mkleehammer
Date 2010-09-17.19:32:09
SpamBayes Score 0.0075145424
Marked as misclassified No
Message-id <1284751931.03.0.894481141092.issue9889@psf.upfronthosting.co.za>
In-reply-to
Content
Using Py_UNICODE* in Python 3 C extensions is significantly more cumbersome than using char* was in Python 2.x.  One addition that could help would be a Py_UNICODE* format type for PyUnicode_FormatV.

Many printf libraries us %S for wchar_t which would have been nicely analogous, but that is already taken for str(obj).
History
Date User Action Args
2010-09-17 19:32:11mkleehammersetrecipients: + mkleehammer
2010-09-17 19:32:11mkleehammersetmessageid: <1284751931.03.0.894481141092.issue9889@psf.upfronthosting.co.za>
2010-09-17 19:32:09mkleehammerlinkissue9889 messages
2010-09-17 19:32:09mkleehammercreate