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

Showing content from http://mail.python.org/pipermail/python-dev/2004-June/045483.html below:

[Python-Dev] Allowing u.encode() to return non-strings

• Previous message: [Python-Dev] Allowing u.encode() to return non-strings
• Next message: [Python-Dev] Allowing u.encode() to return non-strings
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Ok, how about a compromise: .encode() and .decode() of string
> and unicode objects may return string or unicode objects only
> (limiting the set of types to two base types).

This works for me, especially since I expect type inferencers to
collapse the two types (just as they should collapse int and long).

--Guido van Rossum (home page: http://www.python.org/~guido/)

• Previous message: [Python-Dev] Allowing u.encode() to return non-strings
• Next message: [Python-Dev] Allowing u.encode() to return non-strings
• 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