| I've actually read the background on the exception hierarchy (and agree
| with it all), especially other suggestions that GeneratorExit derive
| from BaseException. As I understand it, Guido's objections are
threefold:
[snip]
After waiting a day or so to see if you get any more feedback here
Oops, forgot to mention this:
I wouldn't be opposed to a different extension that would effectively
let me accomplish the same goals... arbitrary exception filters.
Imagine this:
try:
raise GeneratorExit
except ExceptionFilter:
# blah
where Exce
Hi Terry,
Thank you for your feedback. Responses inline:
Terry Reedy wrote:
> "Chad Austin" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> || try:
> | result = yield chatGateway.checkForInvite({'userId': userId})
> | logger.info('checkForInvite2 returned %s', result)
>
> would
"Chad Austin" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
|| try:
| result = yield chatGateway.checkForInvite({'userId': userId})
| logger.info('checkForInvite2 returned %s', result)
would not
except GeneratorExit:
solve your problem?
| except Exception:
Such catchalls are kno
Hi all,
First, I'd like to describe a system that we've built here at IMVU in
order to manage the complexity of our network- and UI-heavy application:
Our application is a standard Windows desktop application, with the main
thread pumping Windows messages as fast as they become available. On
