On Tue, 24 Sep 2013 18:06:15 +1000 Nick Coghlan <ncogh...@gmail.com> wrote: > > How is it wrong? At the point where the interpreter says "This > exception is now unraisable", what, precisely, is it saying that is > wrong? > It isn't saying "this has never been raised". It is saying, "where it > is currently being processed, this exception cannot be raised".
Well, it is saying it. If it's conceptually unraisable, it can't be raised. I know your point is that it is only unraisable *now*, but that's not the intuitive interpretation. > >> Preferring the status quo because > >> you're holding out a forlorn hope for a concise wording that explains: > > > > I've proposed other options. > > "Automatically caught" says nothing about why the exception is being > printed to stderr instead of propagating normally. Exceptions are > automatically caught by any matching except clause all the time, but > most of those don't result in errors printed to stderr. I would say they are manually caught by except clauses (user code == manual intervention), and automatically caught when "silenced" or "unraised" by the interpreter. Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
