➜

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 pitrou
Recipients Arfrever, lemburg, loewis, pitrou, r.david.murray, scoder, stutzbach, vstinner, zooko
Date 2010-09-03.15:38:44
SpamBayes Score 0.03803903
Marked as misclassified No
Message-id <1283528326.42.0.201845886794.issue8654@psf.upfronthosting.co.za>
In-reply-to
Content 
+#undef HAVE_USABLE_CHAR_T

Isn't it HAVE_USABLE_WCHAR_T?

+struct PY_UNICODE_STRUCT;
+typedef struct PY_UNICODE_STRUCT Py_UNICODE_STRUCT;
+#define Py_UNICODE Py_UNICODE_STRUCT

Why not simply `typedef struct PY_UNICODE_STRUCT Py_UNICODE`?

The _testunicodeagnostic module could have a simple test method making a couple of calls to PyUnicode_* functions.
History
Date User Action Args
2010-09-03 15:38:46pitrousetrecipients: + pitrou, lemburg, loewis, zooko, scoder, vstinner, stutzbach, Arfrever, r.david.murray
2010-09-03 15:38:46pitrousetmessageid: <1283528326.42.0.201845886794.issue8654@psf.upfronthosting.co.za>
2010-09-03 15:38:44pitroulinkissue8654 messages
2010-09-03 15:38:44pitroucreate