I'll go back and look again, but as far as I could tell from the .il code and
the .c code for clr.pyd and clr.so...
- clr.so bootstraps mono (under Windows the OS knows how to dlload a .net
assembly already) to enable .net assembly extensions and I assumed perhaps
recklessly that it laterals to
I got it working on MacOSX under Mono. I'm pretty sure the clr.pyd is only for
Windows. I think you just need the Python.Runtime.dll, the
Python.Runtime.dll.config, and the clr.so in the site-packages folder.
Joe
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Be
In the readme, it says that "python for .net uses the pythonpath
(sys.path) to look for assemblies to load, in addition to the usual
application base and the gac.
Unfortunately at the moment the assembly I'm trying to load is... clr.pyd.
If I run python (ubuntu, mono, rebuilt python 2.5.2 with
Feihong Hsu ha scritto:
I believe Brian's assessment is correct. The easiest way to handle this
is to use pywin32's pythoncom module to set the threading model. You can
find a sample of how to do that here:
http://www.ironpython.info/index.php/Using_the_WebBrowser_Widget
In the sample, the We
I figured out the python.exe is a dynamically-linked python for use
under systems like ubuntu where the provided distribution is statically
linked. But I had already installed an overriding distribution of
python from sources.
FYI, ubuntu's distribution is this way because for whatever reason
