aaand one more note: I just re-made the patch (now at
http://sourceforge.net/tracker/index.php?func=detail&aid=1834903&group_i
d=162464&atid=823893 ).
I basically re-wrote clrmodule.il. It's heavily commented now, and
supports loading out of PYTHONPATH (based on idea by Maksim Kozyarchuk).
I
Re-sending to get it posted to the maillist (really don't know how these
work, or how the threading is determined under
http://mail.python.org/pipermail/pythondotnet/2007-November/thread.html
).
Ok, I've submitted the patches. Note that I'm purely Windows here using
the Microsoft .NET fram
I'm talking about Python.NET 2.0. Regardless, you're using the 32-bit
version of Python on your machine, right?
import platform
platform.architecture()
John
From: Feihong Hsu [mailto:[EMAIL PROTECTED]
Sent: Monday, November 19, 2007 7:14 AM
To: John Burnett; [email protected]
S
Are you talking about Python.NET 1.0 or 2.0? I still haven't tried Python.NET
2.0 on my 64-bit workstation, but 1.0 crashes when I try to use Interop
assemblies. I'm not seeing any problems in 1.0 with respect to delegates/events
on x64.
- Feihong
John Burnett <[EMAIL PROTECTED]> wrote: Ad
Still never got the dynamically linked python2.4 to find the assemblies
Python.Runtime. Updating MONO_PATH didn't work.
I ended up taking the C# version python.exe and wrapping it with a shell
script called python2.4 - underneath looks like "mono python.exe"
This version seems to understand MON
