[Zope-Coders] RFC: Death to string exceptions
Paul Winkler
pw_lists at slinkp.com
Mon Nov 17 16:01:43 EST 2003
On Mon, Nov 17, 2003 at 10:27:48AM -0500, Tres Seaver wrote:
> Can anyone thing of a good reason not to exterminate the use of string
> exceptions in the Zope core, both for the 2.7 branch and for the head?
> For instance, are there known (not hypothetical) products which rely on
> them deeply? There are several places where we raise "named" strings;
> clients who already use the names should be safe.
>
> Removing them will silence the majority of deprecation warnings which
> currently pollute the 'make test' output for 2.7.
I was a bit concerned that this would be a problem for Scripts
that might currently catch a string exception and not be allowed to
import the corresponding Exception.
I can't quite bring to mind whatever it was that made me think this
was a potential issue ... maybe some really old mailing list
discussion ... or maybe i'm half-remembering some issue
with a third-party product rather than core zope...
geez, am I senile already?
I guess all I'm saying is that all reasonably safe exceptions
should be importable for TTW code.
But I just did a search of all my current Python Scripts and
didn't find any of these, so maybe it's not a real problem?
--
Paul Winkler
http://www.slinkp.com
Look! Up in the sky! It's SUPER PERFUME MONOTREME!
(random hero from isometric.spaceninja.com)
More information about the Zope-Coders
mailing list