It is way past time that the pywin32 exception objects grew attributes
instead of only being available via indexing. In other words, instead of
writing:
except win32api.error, exc:
if exc[0] == ERROR_CODE: ...
you can say:
except win32api.error, exc:
if exc.winerror == ERROR_CODE:
Mark,
exc.excepinfo == exc[2] - named after the win32 EXCEPINFO struct. Remains
a tuple without attributes.
Would'nt it be a good point to use a named tuple, at least on Pythons
where that is available?
Does anyone see a problem with that?
Not me.
Harald
--
GHUM Harald Massa
Hi
I have a C++ program which embeds Python and is itself modularized
into several DLLs. The Python part (extensions) of the application
again links to these DLLs, the problem is the containing catalog (also
containing the executable itself) is not on the PATH, so the DLLs
aren't resolved when
If you didn't get the answer already, you need to call pythoncom.CoInitialize()
prior to the code that is throwing an error,
probably put it right after init.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of [EMAIL PROTECTED]
Sent: Monday, September 29,
Hello,
Is it possible to tell windows to wait a python service has started
before the login prompt is displayed ?
___
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
le dahut wrote:
Hello,
Is it possible to tell windows to wait a python service has started
before the login prompt is displayed ?
Probably not, but why would you want to implement something that does? Share
your use case with us and perhaps we can be of more assistance.
-Larry
