On 2/10/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 1/29/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > I was more generally wondering what the plan was for transitioning any
> > C API changes (if we were even going to do that level of transition).
>
> It's too early for much of a plan IM
Brett Cannon schrieb:
> This has come up before on python-dev, IIRC. Double-check the archives.
More specifically, see PEP 294. It claims the types module will be
removed in Python 3000.
Regards,
Martin
___
Python-3000 mailing list
Python-3000@python.
Brett Cannon schrieb:
> 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. But not allowing -1 to
On 2/11/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
> > 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
> >
On 2/11/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
> > This has come up before on python-dev, IIRC. Double-check the archives.
>
> More specifically, see PEP 294. It claims the types module will be
> removed in Python 3000.
Is removing the types module still a goal?
Well, I would surely love to see it replaced by something more reasonable.
Collecting type objects together just on the basis that they are all
built-in type objects was a bad idea.
I still hope to do something about Bill Janssen's ABC proposal. But
that will have to wait until after PyCon.
--Gu
Brett Cannon schrieb:
> Right, but I wanted to be able to raise a warning. If that warning is
> supposed to be treated as an exception the caller needs to let that
> propagate. RIght now PyErr_GivenExceptionMatches() can in no way let
> the caller know that fact
I'm unclear why you want to warn
