On 3/2/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> > I think the slice removal is easy. But getting rid of 'args' and
> > making BaseException's constructor only take a single argument is not
> > painless. But a warning should help get this done in a reasonable
> > fashion
Brett Cannon wrote:
> I think the slice removal is easy. But getting rid of 'args' and
> making BaseException's constructor only take a single argument is not
> painless. But a warning should help get this done in a reasonable
> fashion.
The exception slicing is the only thing I ever thought was
On 3/2/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> On 3/1/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > I spent my sprint time cleaning up exceptions for Py3K and Guido
> > suggested I run some things by the group to make sure they don't make
> > transitioning from 2.6 too difficult. After ad
On 3/1/07, Brett Cannon <[EMAIL PROTECTED]> wrote:
> I spent my sprint time cleaning up exceptions for Py3K and Guido
> suggested I run some things by the group to make sure they don't make
> transitioning from 2.6 too difficult. After adding the proper
> restrictions in terms of what can and cann
I spent my sprint time cleaning up exceptions for Py3K and Guido
suggested I run some things by the group to make sure they don't make
transitioning from 2.6 too difficult. After adding the proper
restrictions in terms of what can and cannot be raised or caught, I
began cleaning up BaseException's
