Message98676
| Author |
lemburg |
| Recipients |
Rhamphoryncus, ajaksu2, amaury.forgeotdarc, benjamin.peterson, collinwinter, eric.smith, ezio.melotti, ferringb, gvanrossum, jafo, jimjjewett, lemburg, mark.dickinson, orivej, pitrou, rhettinger, terry.reedy |
| Date |
2010年02月01日.19:21:41 |
| SpamBayes Score |
4.1637623e-08 |
| Marked as misclassified |
No |
| Message-id |
<4B6729C4.7010002@egenix.com> |
| In-reply-to |
<1265046905.95.0.606077927564.issue1943@psf.upfronthosting.co.za> |
| Content |
modules to py3k.
> This is not an implementation detail.
It is, otherwise I would have documented it. The fact that some
developers are not using those APIs correctly doesn't change that.
Note that PyUnicode_AsUnicode() only returns a pointer to the
Py_UNICODE buffer. It makes no guarantees on the 0-termination.
Developers need to use PyUnicode_GetSize() to access the size
of the Unicode string.
But no worries: We're not going to change it. It's too late
after 10 years in the wild.
Still, developers will have to be aware of the fact that 0-termination
is not a guaranteed Unicode feature and should stop making that
assumption and it will not necessarily hold or be guaranteed
for Unicode subclasses. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年02月01日 19:21:44 | lemburg | set | recipients:
+ lemburg, gvanrossum, collinwinter, rhettinger, terry.reedy, jafo, jimjjewett, amaury.forgeotdarc, mark.dickinson, Rhamphoryncus, pitrou, eric.smith, ferringb, ajaksu2, benjamin.peterson, orivej, ezio.melotti |
| 2010年02月01日 19:21:41 | lemburg | link | issue1943 messages |
| 2010年02月01日 19:21:41 | lemburg | create |
|