Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2002-April/023011.html below:

[Python-Dev] Regression in unicodestr.encode()?

• Previous message: [Python-Dev] Regression in unicodestr.encode()?
• Next message: [Python-Dev] Regression in unicodestr.encode()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

"M.-A. Lemburg" <mal@lemburg.com> writes:

> > It's a UTF-8 codec bug. The codec writes over the end of the buffer,
> > then invokes resize. Resizing only copies the allocated bytes, hence
> > the uninitialized bytes at the end.
> 
> Ah, yes, you're right.

Thanks :-) I think the right fix is to avoid any resizing in the UTF-8
codec; that has bitten way too often now. Instead, it should establish
the size of the string first, then perform the actual encoding.

Regards,
Martin

• Previous message: [Python-Dev] Regression in unicodestr.encode()?
• Next message: [Python-Dev] Regression in unicodestr.encode()?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4