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

Showing content from https://mail.python.org/pipermail/python-dev/2000-April/003165.html below:

[Python-Dev] Re: unicode: strange exception (part 2)

• Previous message: [Python-Dev] Why do we need Traceback Objects?
• Next message: [Python-Dev] Re: unicode: strange exception (part 2)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I wrote:

> >>> "!" in ("a", None)
> 0
> >>> u"!" in ("a", None)
> Traceback (innermost last):
>   File "<stdin>", line 1, in ?
> TypeError: expected a character buffer object

with the latest version, I get:

>>> "!" in ("a", None)
0
>>> u"!" in ("a", None)
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
TypeError: coercing to Unicode: need string or charbuffer

is this really an improvement?

looks like writing code that works with any kind of strings
will be harder than I thought...

</F>

• Previous message: [Python-Dev] Why do we need Traceback Objects?
• Next message: [Python-Dev] Re: unicode: strange exception (part 2)
• 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