Clear sys.last_type/value/traceback before checking for leaked objects
commit17709b4997dbb0d943ededf825c698cd045b9db8
authorOwen W. Taylor <otaylor@fishsoup.net>
Sat, 15 Oct 2011 17:46:29 +0000 (15 13:46 -0400)
committerOwen W. Taylor <otaylor@fishsoup.net>
Sat, 15 Oct 2011 17:46:29 +0000 (15 13:46 -0400)
tree9c4e0635af8ddb086073c539d9313970292c0506
parent8fd9390681744a302c4c0f82b74b07189651edf6
Clear sys.last_type/value/traceback before checking for leaked objects

If an exception was thrown and caught by the PyGObject runtime, that
would result in spurious apparent leaks because of the traceback
that was stored away in the sys module.
bin/uninst.py