Guido van Rossum wrote:
> If I understand correctly what you are referring to, this is a
> feature. You're supposed to say:
>
> try:
> return f()
> except:
> pass
> sys.exc_info()
>
> i.e. the exc_info() must remain accessible.
Aha! Yup! Thanks.
Then, it is probably not a bug but a feature.
Would it be ok then, if I write a function
that exposes reset_exc_info to the user?
sys.exc_clear() # maybe?
Or a function which returns *and* clears the exc?
tup = sys.exc_info_reset()
ciao - chris
--
Christian Tismer :^) <mailto:tismer@tismer.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 pager +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4