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

Showing content from https://mail.python.org/pipermail/python-dev/2009-January/084889.html below:

[Python-Dev] Decoder functions accept str in py3k

• Previous message: [Python-Dev] Decoder functions accept str in py3k
• Next message: [Python-Dev] Decoder functions accept str in py3k
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Jan 7, 2009 at 9:46 AM, Guido van Rossum <guido at python.org> wrote:
> A -3 warning should be added to 2.6 about this too IMO.

A Py3k warning when attempting to decode a unicode string? Wouldn't
that open the door to adding warnings to everywhere a unicode string
is used where a byte string is? I thought that unicode and str's
compatibility was quite intentionally not being touched until 3.0.


-- 
Regards,
Benjamin

• Previous message: [Python-Dev] Decoder functions accept str in py3k
• Next message: [Python-Dev] Decoder functions accept str in py3k
• 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