[Python-3000] how should we handle changes to the C API?

[Greg Ewing]

Brett Cannon wrote:

> My specific need is that PyErr_GivenExceptionMatches() does not have
> an exception return value.  This sucks for me in 2.6 for deprecating
> catching string exceptions, but it sucks more in 3.0 since only
> subclasses of BaseException can be raised.

Given that this would only be really useful during
the transition to wean people off string and/or non
BaseExceptions, do we really want to make a permanent
change to the API with all the upheaval it would
cause?

Seems to me you can still generate a warning for
these things, you just wouldn't be able to escalate
them into errors.

--
Greg