Re: Importing WMI in a child Thread throws an error

2007-03-15 Thread Tim Golden
>> If you want to post some specific code examples, I'm >> happy to talk you through possible optimisations. >> >> TJG > > Sorry I didn't reply right away. Here's the straight WMI code I'm > using: > > c = wmi.WMI() > for i in c.Win32_ComputerSystem(): > mem = int(i.TotalPhysicalMemor

Re: Importing WMI in a child Thread throws an error

2007-03-15 Thread kyosohma
On Feb 28, 3:08 pm, Tim Golden <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > On Feb 27, 3:32 pm, Tim Golden <[EMAIL PROTECTED]> wrote: > >> [EMAIL PROTECTED] wrote: > >>> The problem I have is that since I import WMI, it takes a long time > >>> and we have users complaining about it. So

Re: Importing WMI in a child Thread throws an error

2007-02-28 Thread Tim Golden
[EMAIL PROTECTED] wrote: > On Feb 27, 3:32 pm, Tim Golden <[EMAIL PROTECTED]> wrote: >> [EMAIL PROTECTED] wrote: >>> The problem I have is that since I import WMI, it takes a long time >>> and we have users complaining about it. So I stuck the import >>> statement into a separate thread and set it

Re: Importing WMI in a child Thread throws an error

2007-02-28 Thread kyosohma
On Feb 27, 3:32 pm, Tim Golden <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > The problem I have is that since I import WMI, it takes a long time > > and we have users complaining about it. So I stuck the import > > statement into a separate thread and set it to a daemon so it could do >

Re: Importing WMI in a child Thread throws an error

2007-02-27 Thread Tim Golden
[EMAIL PROTECTED] wrote: > The problem I have is that since I import WMI, it takes a long time > and we have users complaining about it. So I stuck the import > statement into a separate thread and set it to a daemon so it could do > its thing in the background and the rest of the script would fin