Message117882
| Author |
vstinner |
| Recipients |
ezio.melotti, lemburg, stutzbach, theller, vstinner |
| Date |
2010年10月02日.15:29:09 |
| SpamBayes Score |
2.3944957e-11 |
| Marked as misclassified |
No |
| Message-id |
<1286033351.28.0.899090291534.issue8670@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> Since this was a bugfix, it should be merged back into 2.7, yes?
Mmmh, the fix requires to change PyUnicode_AsWideChar() function (support non-BMP characters and surrogate pairs) (and maybe also to create PyUnicode_AsWideCharString()). I don't really want to change such important function in a stable branch (Python2).
Is it really important to support non-BMP characters for ctypes.c_wchar in Python2? I would like to say: if you want better unicode support, use Python 3. And Python 3.2 if it's possible :-) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年10月02日 15:29:11 | vstinner | set | recipients:
+ vstinner, lemburg, theller, stutzbach, ezio.melotti |
| 2010年10月02日 15:29:11 | vstinner | set | messageid: <1286033351.28.0.899090291534.issue8670@psf.upfronthosting.co.za> |
| 2010年10月02日 15:29:09 | vstinner | link | issue8670 messages |
| 2010年10月02日 15:29:09 | vstinner | create |
|