Message135369
| Author | loewis |
|---|---|
| Recipients | dcoles, lemburg, loewis, pitrou, vstinner |
| Date | 2011-05-06.21:24:54 |
| SpamBayes Score | 0.0001717332 |
| Marked as misclassified | No |
| Message-id | <1304717095.82.0.106731542637.issue12010@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think what they mean is a better representation from an Android API, such as UChar32 from utils/AndroidUnicode.h. I agree that it's not worthwhile trying to port Python to those Android versions that have a single-byte wchar_t definition. David, I think you are misunderstanding the purpose of HAVE_USABLE_WCHAR_T: It does *not* specify whether wchar_t can be used. Instead, it specifies whether wchar_t can be used as the datatype for Py_UNICODE. Calling it HAVE_A_WCHAR_T_DEFINITION_THAT_IS_SUITABLE_FOR_USE_AS_BASE_TYPE_OF_PY_UNICODE was just a little too tedious :-) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-05-06 21:24:55 | loewis | set | recipients: + loewis, lemburg, pitrou, vstinner, dcoles |
| 2011-05-06 21:24:55 | loewis | set | messageid: <1304717095.82.0.106731542637.issue12010@psf.upfronthosting.co.za> |
| 2011-05-06 21:24:55 | loewis | link | issue12010 messages |
| 2011-05-06 21:24:54 | loewis | create | |