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

Showing content from http://mail.python.org/pipermail/python-dev/2002-April/023014.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:

> > Ah, yes, you're right.
> 
> That is... instrumenting the codec I get these results:
[...]
> cbWritten=126, cbAllocated=144
> end of string = 'ck git und'
> '\xe6\xad\xa3\xe7\xa2\xba\xe3....das Nunstuck git u \x8f'
> 
> (the last two bytes seem to be random data, they change 
> from run to run)

Are you saying it does not write past cbAllocated? It certainly does:
Just check then length of the encoded string. In the corrected
version, the proper length of the encoded string is 158.

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