[issue1950] Potential overflows due to incorrect usage of PyUnicode_AsString.

Marc-Andre Lemburg report at bugs.python.org
Sat May 3 21:53:28 CEST 2008


Marc-Andre Lemburg <mal at egenix.com> added the comment:

On 2008-05-03 20:25, Alexandre Vassalotti wrote:
> Alexandre Vassalotti <alexandre at peadrop.com> added the comment:
> 
> Committed to r62667.
> 
> Thank you all for your comments!
> 
> ----------
> resolution:  -> fixed
> status: open -> closed

What about my comments regarding the PyUnicode_AsString() API in
http://bugs.python.org/msg65962

Should I open a separate tracker item for this ?

I don't know who added those APIs, but they are neither in line with
the rest of the Unicode API, nor are they really all that helpful.
I guess they were just added out of a misunderstanding of the
already existing code.

I'd suggest to remove PyUnicode_AsString() altogether (which your
patch has already done in a couple of places).

----------
title: Potential overflows due to incorrect usage of PyUnicode_AsString. -> Potential overflows due to incorrect usage of	PyUnicode_AsString.

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1950>
__________________________________


More information about the Python-bugs-list mailing list