Re: [Python-Dev] PEP 352 Transition Plan

2005-11-05 Thread Guido van Rossum
[Guido van Rossum] I've made a final pass over PEP 352, mostly fixing the __str__, __unicode__ and __repr__ methods to behave more reasonably. I'm all for accepting it now. Does anybody see any last-minute show-stopping problems with it? [François] I did not follow the thread, so maybe

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-31 Thread Guido van Rossum
I've made a final pass over PEP 352, mostly fixing the __str__, __unicode__ and __repr__ methods to behave more reasonably. I'm all for accepting it now. Does anybody see any last-minute show-stopping problems with it? As always, http://python.org/peps/pep-0352.html -- --Guido van Rossum (home

[Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Raymond Hettinger
I don't follow why the PEP deprecates catching a category of exceptions in a different release than it deprecates raising them. Why would a release allow catching something that cannot be raised? I must be missing something here. Raymond ___

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Guido van Rossum
On 10/28/05, Raymond Hettinger [EMAIL PROTECTED] wrote: I don't follow why the PEP deprecates catching a category of exceptions in a different release than it deprecates raising them. Why would a release allow catching something that cannot be raised? I must be missing something here. So

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Adam Olsen
On 10/28/05, Raymond Hettinger [EMAIL PROTECTED] wrote: I don't follow why the PEP deprecates catching a category of exceptions in a different release than it deprecates raising them. Why would a release allow catching something that cannot be raised? I must be missing something here.

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Brett Cannon
On 10/28/05, Raymond Hettinger [EMAIL PROTECTED] wrote: Why would a release allow catching something that cannot be raised? I must be missing something here. So conforming code can catch exceptions raised by not-yet conforming code. That makes sense. What was the rationale for

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Nick Coghlan
Brett Cannon wrote: Interesting point, but I think that chaining should have more concrete support ala PEP 344 or some other mechanism. I think most people agree that exception chaining is important enough to have better support than some implied way of a causing exception to be passed

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Raymond Hettinger
[Nick Coghlan] Another point in PEP 352's favour, is that it makes it far more feasible to implement something like PEP 344 by providing __traceback__ and __prev_exc__ attributes on BaseException. The 'raise' statement could then take care of setting them appropriately if it was given an

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Brett Cannon
On 10/28/05, Nick Coghlan [EMAIL PROTECTED] wrote: Brett Cannon wrote: Interesting point, but I think that chaining should have more concrete support ala PEP 344 or some other mechanism. I think most people agree that exception chaining is important enough to have better support than

Re: [Python-Dev] PEP 352 Transition Plan

2005-10-28 Thread Christopher Armstrong
On 10/29/05, Nick Coghlan [EMAIL PROTECTED] wrote: Another point in PEP 352's favour, is that it makes it far more feasible to implement something like PEP 344 by providing __traceback__ and __prev_exc__ attributes on BaseException. Not sure if I'm fully in-context here, but watch out for