On Thu, Apr 21, 2005 at 11:29:38AM +0200, Dag Wieers <[EMAIL PROTECTED]> wrote:
> I can repeat this, but it's more like within the first miliseconds.
Fast system with no activity :) On my dual-P3 1Ghz dstat usually needs
around 4 seconds to start up. On my dual 600mhz p3 machine it can take up
to 10 seconds.
> I'm not sure if the proper thing to do is to import the python modules
> within my try-block.
I have no idea, either, but the proper thing to do would be not to display
any tracebacks or anything. My biggest grief with many python programs
(bittorrent for example) is that they love to output tracebacks without
exiting when ^INT :)
I guess the best thing is to only catching INT before initscr, as before
there is no reaosn even to catch the signal, because catching it only adds
time before the user gets back at his/her prompt (there is nothing to
cleanup), although I suspect that it can't be done with python.
> I noticed eg. that yum only imports sys before importing everything else
> in a try-block. Which reduces the chance of being hit by this.
The important thing is that it can be reproduced.
However, despite me bashing on this, it really is a very very minor issue
:)
--
The choice of a
-----==- _GNU_
----==-- _ generation Marc Lehmann
---==---(_)__ __ ____ __ [EMAIL PROTECTED]
--==---/ / _ \/ // /\ \/ / http://schmorp.de/
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
