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 | amaury.forgeotdarc, benjamin.peterson, georg.brandl, lemburg, pitrou, schuppenies |
| Date | 2008年06月13日.19:56:46 |
| SpamBayes Score | 0.39687428 |
| Marked as misclassified | No |
| Message-id | <1213387007.78.0.997183118146.issue3098@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Hmm, so it seems that in some UCS4 builds, sizeof(Py_UNICODE) could end up being more than 4 if the native int type is itself larger than 32 bits; although the latter is probably quite rare (64-bit platforms are usually either LP64 or LLP64). However, Py_UNICODE.patch is wrong in that it uses Py_UNICODE_SIZE rather than sizeof(Py_UNICODE). Py_UNICODE_SIZE itself is always either 2 or 4. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年06月13日 19:56:48 | pitrou | set | spambayes_score: 0.396874 -> 0.39687428 recipients: + pitrou, lemburg, georg.brandl, amaury.forgeotdarc, benjamin.peterson, schuppenies |
| 2008年06月13日 19:56:47 | pitrou | set | spambayes_score: 0.396874 -> 0.396874 messageid: <1213387007.78.0.997183118146.issue3098@psf.upfronthosting.co.za> |
| 2008年06月13日 19:56:47 | pitrou | link | issue3098 messages |
| 2008年06月13日 19:56:46 | pitrou | create | |