Nick Coghlan wrote: > I have a Python 2.5 candidate hierarchy below, which uses dual inheritance to > avoid breaking backward compatibility - any existing except clauses will > catch > all of the exceptions they used to catch. The only new inheritance introduced > is to new exceptions, also avoiding backward compatibility problems, as any > existing except clauses will let by all of the exceptions they used to let > by. > There are no removals, but the deprecation process is started in order to > change the names of ReferenceError and RuntimeWarning to WeakReferenceError > and SemanticsWarning.
+1. I like this approach of using multiple inheritence to solve the b/w compatibility problem. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Aug 02 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! :::: _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
