The CLR always loads up ole32 at startup and will even if it didn't it'd need
to for the [STAThread] attribute.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Reade
Sent: Friday, November 07, 2008 4:03 AM
To: Discussion of IronPython
Subject:
Ori Peleg wrote:
[snip...]
BTW - the use case is for building test suites: you can have a
subpackage of tests and define __init__.py like this:
def suite():
import testoob
return testoob.collecting.collect_from_files(test_*.py)
Why not change the API to:
return
Thanks Dino -- you've given me plenty to be going on with until you hear
back from the CLR dev.
Dino Viehland wrote:
In MTA mode we'll create a new thread which is thread 3 - thread 1 will just be
hanging around waiting for it to exit. Unfortunately w/o a separate EXE we
can't avoid the
So far as I can tell, CPython ctypes and installers (neither of which
are currently relevant) use COM, and numpy doesn't use it at all.
However, my search wasn't very sophisticated -- I just looked for
CoInitialize, CoCreateInstance, and lpVtbl, which is all the COM I can
remember*. Was that
I'll look into that along with everything else :).
Dino Viehland wrote:
Do you know if numpy is using COM anywhere? Or does Ironclad use COM for any
of its interop?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Reade
Sent: Thursday,
