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

Showing content from https://mail.python.org/pipermail/python-dev/2004-June/045482.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 ]

Jeremy Hylton wrote:
> Who cares about the type inference <0.2 wink>.  It's harder for the
> reader of the program to understand if encode() returns a different
> type.  Would there be some common property that all encode() return
> values would share?  Can't think of one myself.

No. In addition, the stream codec classes become meaningless 
(StreamReader, StreamWriter), as they are supposed to return
a concatenation of encoding results - however, there is no
guarantee that the encoding results even can be concatenated.

Regards,
Martin

• 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