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

Showing content from http://mail.python.org/pipermail/python-dev/2002-March/021796.html below:

[Python-Dev] Deprecating string exceptions

• Previous message: [Python-Dev] Deprecating string exceptions
• Next message: [Python-Dev] Deprecating string exceptions
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Should it be arbitrary objects or just subclasses of exception: "It is
> recommended that user-defined exceptions in new code be derived from
> Exception, although for backward compatibility reasons, this is not
> required. Eventually this rule will be tightened."

Can we safely make Exception (and hence all built-in exceptions) a
new-style class?  This could break user code (even when we don't
enforce that exceptions are derived from Exception).

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

• Previous message: [Python-Dev] Deprecating string exceptions
• Next message: [Python-Dev] Deprecating string exceptions
• 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