From c1dd174682e1bce7044ae993bfadc3a042a53ed6 Mon Sep 17 00:00:00 2001 From: "Andrew M. Kuchling" Date: Mon, 13 Jan 2003 13:59:22 +0000 Subject: Link to MRO article Mention deprecation of string exceptions --- Doc/whatsnew/whatsnew23.tex | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/Doc/whatsnew/whatsnew23.tex b/Doc/whatsnew/whatsnew23.tex index c97a544..26a8e30 100644 --- a/Doc/whatsnew/whatsnew23.tex +++ b/Doc/whatsnew/whatsnew23.tex @@ -1054,6 +1054,10 @@ check for use of features that will be deprecated in the future, supply \programopt{-Walways::PendingDeprecationWarning::} on the command line or use \function{warnings.filterwarnings()}. +\item The process of deprecating string-based exceptions, as +in \code{raise "Error occurred"}, has begun. Raising a string will +now trigger \exception{PendingDeprecationWarning}. + \item Using \code{None} as a variable name will now result in a \exception{SyntaxWarning} warning. In a future version of Python, \code{None} may finally become a keyword. @@ -1065,8 +1069,10 @@ this change.) Python 2.2 originally used a topological sort of a class's ancestors, but 2.3 now uses the C3 algorithm as described in the paper \ulink{``A Monotonic Superclass Linearization for Dylan''}{http://www.webcom.com/haahr/dylan/linearization-oopsla96.html}. -To understand the motivation for this change, read the thread on -python-dev starting with the message at +To understand the motivation for this change, +read Michele Simionato's article +\ulink{``Python 2.3 Method Resolution Order''}{http://www.phyast.pitt.edu/~micheles/mro.html}, or +read the thread on python-dev starting with the message at \url{http://mail.python.org/pipermail/python-dev/2002-October/029035.html}. Samuele Pedroni first pointed out the problem and also implemented the fix by coding the C3 algorithm. -- cgit v0.12