[python-win32] Threads in COM not given time to execute?

Marcus Low marcus at internetnowasp.net
Mon Mar 31 11:23:26 CEST 2008


Found the reason. The COM component in this case somehow depends on the windows message pump.

    while FlagToStop == False :

Solved the issue.

  ----- Original Message ----- 
  From: Marcus Low 
  To: 'Python-Win32 List' 
  Sent: Monday, March 31, 2008 4:48 PM
  Subject: [python-win32] Threads in COM not given time to execute?


  I am testing a COM component, when i execute it under pythonwin idle and single stepping F10 to "SmtpMail.Start()" :

      SmtpMail = win32com.client.Dispatch("SomeSMTPCom")
  I can telnet to 25 and get a proper SMTP response

  But when i run the program it just quits so i am assuming SmtpMail.Start() does not block. So i added a function to wait for an event
  before allowing the function to quit to that SmtpMail.Start() can run as long as it want :-

  def MainEntry () :
      global FlagToStop

      SmtpMail = win32com.client.Dispatch("SomeSMTPCom")
      while FlagToStop == False :
          win32api.Sleep(1000)      # i tried os.sleep(0), pass but the uses 50% of cpu


  i have confirmed that the it will loop in "While FlagToStop ..." however when i telnet 25, it gets connected but i don't get a reply from the COM which
  is a STMP component. I can get a response if i use single step to where ".Start()" but if i just run the program i get this feeling that the COM object here doesnt
  get the time to execute and thus could not respond.

  Am i missing out some basic steps here?



  python-win32 mailing list
  python-win32 at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-win32/attachments/20080331/f119d6a9/attachment-0001.htm 

More information about the python-win32 mailing list