(sorry for the delayed reply; vacation)
On Aug 14, 2005, at 12:27 PM, Guido van Rossum wrote:
On 8/14/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
Wilfredo Sánchez Vega <[EMAIL PROTECTED]> writes:
I'm curious about why Python lacks FileNotFoundError,
PermissionError and the like as su
(sorry for the delayed reply; vacation)
On Aug 14, 2005, at 12:27 PM, Guido van Rossum wrote:
On 8/14/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
Wilfredo S
ánchez Vega <[EMAIL PROTECTED]> writes:
I'm curious about why Python lacks FileNotFoundError,
PermissionError and the li
On 8/14/05, Michael Hudson <[EMAIL PROTECTED]> wrote:
> Wilfredo Sánchez Vega <[EMAIL PROTECTED]> writes:
>
> >I'm curious about why Python lacks FileNotFoundError,
> > PermissionError and the like as subclasses of IOError.
>
> Good question. Lack of effort/inertia?
Well, I wonder how often
Wilfredo Sánchez Vega <[EMAIL PROTECTED]> writes:
>I'm curious about why Python lacks FileNotFoundError,
> PermissionError and the like as subclasses of IOError.
Good question. Lack of effort/inertia?
>Catching IOError and looking at errno to figure out what went
> wrong seems prett
I'm curious about why Python lacks FileNotFoundError,
PermissionError and the like as subclasses of IOError.
Catching IOError and looking at errno to figure out what went
wrong seems pretty unpythonic, and I've often wished for built-in
subclasses of IOError.
I sometimes subclass t
> > > > >+-- NamespaceError (rename of NameError)
> > > > >+-- UnboundFreeError (new)
> > > > >+-- UnboundGlobalError (new)
> > > > >+-- UnboundLocalError
> > > > >
> > > >
> > > > What are these new exceptions for? Under what circumstances are
they
> > >
On 8/5/05, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> > On 8/4/05, James Y Knight <[EMAIL PROTECTED]> wrote:
> > > >+-- NamespaceError (rename of NameError)
> > > >+-- UnboundFreeError (new)
> > > >+-- UnboundGlobalError (new)
> > > >+-- UnboundLocalE
On 8/5/05, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On 8/5/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > On 8/4/05, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> >
> > > This does contradict my earlier claim that Python itself doesn't use
> > > RuntimeError; I think I'd be happier if it rema
Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 8/4/05, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> I just realized that keeping RuntimeError still does not resolve the
> issue that the name kind of sucks for realizing intrinsically that it
> is for quick-and-dirty exceptions (or am I the only on
On 8/5/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> On 8/4/05, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>
> > This does contradict my earlier claim that Python itself doesn't use
> > RuntimeError; I think I'd be happier if it remained RuntimeError. (I
> > think there are a few more uses of it
On 8/4/05, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> This does contradict my earlier claim that Python itself doesn't use
> RuntimeError; I think I'd be happier if it remained RuntimeError. (I
> think there are a few more uses of it inside Python itself; I don't
> think it's worth inventing ne
On 8/4/05, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> In general the PEP looks really good now!
>
Glad you like it.
> On 8/4/05, Willem Broekema <[EMAIL PROTECTED]> wrote:
> > On 8/4/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > > OK, once the cron job comes around and is run,
> > > http://
On 8/4/05, James Y Knight <[EMAIL PROTECTED]> wrote:
> >+-- NamespaceError (rename of NameError)
> >+-- UnboundFreeError (new)
> >+-- UnboundGlobalError (new)
> >+-- UnboundLocalError
> >
>
> What are these new exceptions for? Under what circumstances ar
On 8/4/05, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Since I forgot to mention it in the last couple of messages - this version
> looks very good. The transition strategy section makes it a lot more
> meaningful.
>
Great to hear!
> Brett Cannon wrote (in the PEP):
> > Renamed Exceptions
> >
> >
On 8/4/05, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote (in the PEP):
> > KeyboardInterrupt inheriting from ControlFlowException
> >
> > KeyboardInterrupt has been a contentious point within this hierarchy. Some
> > view the exception as more control flow being caused by the user. B
In general the PEP looks really good now!
On 8/4/05, Willem Broekema <[EMAIL PROTECTED]> wrote:
> On 8/4/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> > OK, once the cron job comes around and is run,
> > http://www.python.org/peps/pep-0348.html will not be a 404 but be the
> > latest version of th
>+-- NamespaceError (rename of NameError)
>+-- UnboundFreeError (new)
>+-- UnboundGlobalError (new)
>+-- UnboundLocalError
>
What are these new exceptions for? Under what circumstances are they
raised? Why is this necessary or an improvement?
> Rename
On 8/4/05, Brett Cannon <[EMAIL PROTECTED]> wrote:
> OK, once the cron job comes around and is run,
> http://www.python.org/peps/pep-0348.html will not be a 404 but be the
> latest version of the PEP.
Currently, when the "recursion limit" is reached, a RuntimeError is
raised. RuntimeError is in th
On Aug 4, 2005, at 7:03 AM, Nick Coghlan wrote:
> Additionally, consider that a hypothetical ThreadExit exception
> (used to
> terminate a thread semi-gracefully) would also clearly belong under
> ControlFlowException. That is, just because something is
> asynchronous with
> respect to the curr
Since I forgot to mention it in the last couple of messages - this version
looks very good. The transition strategy section makes it a lot more meaningful.
Brett Cannon wrote (in the PEP):
> Renamed Exceptions
>
> Renamed exceptions will directly subclass the new names. When the old
> exceptions
Brett Cannon wrote (in the PEP):
> KeyboardInterrupt inheriting from ControlFlowException
>
> KeyboardInterrupt has been a contentious point within this hierarchy. Some
> view the exception as more control flow being caused by the user. But with
> its asynchronous cause thanks to the user being ab
Nick Coghlan wrote:
> If/when you add a "Getting there from here" section, it would be worth noting
> that there are a few basic strategies to be applied:
Eh, never mind. It's already there ;)
Cheers,
Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
-
Brett Cannon wrote:
> OK, once the cron job comes around and is run,
> http://www.python.org/peps/pep-0348.html will not be a 404 but be the
> latest version of the PEP.
>
> Differences since my last public version is that it has
> BaseException/Exception as the naming hierarchy, Warning inherits
OK, once the cron job comes around and is run,
http://www.python.org/peps/pep-0348.html will not be a 404 but be the
latest version of the PEP.
Differences since my last public version is that it has
BaseException/Exception as the naming hierarchy, Warning inherits from
Exception, UserException is
24 matches
Mail list logo
