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

Showing content from https://mail.python.org/pipermail/python-dev/2001-October/017867.html below:

[Python-Dev] Bug or feature? Unicode vs t#

• Previous message: [Python-Dev] Bug or feature? Unicode vs t#
• Next message: [Python-Dev] Bug or feature? Unicode vs t#
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Tim Peters wrote:
> 
>...
> 
> In 2.1.1, it's '61' instead.  I don't know what ought to happen, but 2.1.1
> suprised me less.  binascii inherits its view of the argument via
> PyArg_ParseTuple's t# code.

The documentation for hexlify says: "Return the hexadecimal
representation of the binary data." I don't think it should accept a
Unicode string as input at all. 

 Paul Prescod

• Previous message: [Python-Dev] Bug or feature? Unicode vs t#
• Next message: [Python-Dev] Bug or feature? Unicode vs t#
• 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