Message81057
| Author |
amaury.forgeotdarc |
| Recipients |
amaury.forgeotdarc, bupjae, ezio.melotti, lemburg, vstinner |
| Date |
2009年02月03日.13:50:11 |
| SpamBayes Score |
5.835492e-07 |
| Marked as misclassified |
No |
| Message-id |
<1233669013.15.0.414055262607.issue5127@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> That would cause major breakage in the C API
Not if you recompile. I don't see how this breaks the API at the C level.
> and is not inline with the intention of having a Py_UNICODE
> type in the first place.
Py_UNICODE is still used as the allocation unit for unicode strings.
To get correct results, we need a way to access the whole unicode
database even on ucs2 builds; it's possible with the unicodedata module,
why not from C?
My motivation for the change is this post:
http://mail.python.org/pipermail/python-dev/2008-July/080900.html |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年02月03日 13:50:13 | amaury.forgeotdarc | set | recipients:
+ amaury.forgeotdarc, lemburg, vstinner, ezio.melotti, bupjae |
| 2009年02月03日 13:50:13 | amaury.forgeotdarc | set | messageid: <1233669013.15.0.414055262607.issue5127@psf.upfronthosting.co.za> |
| 2009年02月03日 13:50:11 | amaury.forgeotdarc | link | issue5127 messages |
| 2009年02月03日 13:50:11 | amaury.forgeotdarc | create |
|