On Thu, 5 Jul 2007, Panu Matilainen wrote:
In practise it means a custom sys.excepthook couldn't be
called while rpmdb/iterators are active. Not a problem for yum where the
output is text-based anyway (the traceback can be printed), but for things
like pirut which probably have their own handler to give pretty tracebacks
to GUI, it is.
right - not so much on the joy for us.
Heh, actually found a wonderfully wacko "minimal impact" way around this:
I just need to hook up to Pythons at-exit chain. Nothing kludgy about that
as such, but in order to have rpmdbCheckSignals() to do the necessary
cleanup work in case of a traceback, it needs to send a termination signal
to itself to trigger the cleanup and exit path.
I'll need to think about it some more, don't want to get weird
side-effects from bogus signals, but I might put a patch to rawhide for a
test-drive.
What's really needed though is a sane API to mop up any leftover junk
without unwanted side-effects such as exit()
- Panu -
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
