y, this is known as windows-only. for mono we'd probably have to do a regular python C extension that uses the mono hosting apis to bootstrap the runtime.
-Brian On 10/19/07 7:45 AM, "Christian Heimes" <[EMAIL PROTECTED]> wrote: > Paul Harter wrote: >> Hi, >> >> We are tring to move to python 2.5. and are having trouble getting >> pythonDotNet to import using the pre-built binaries. When we use the >> python.exe which is part of the pre-built binaries "import clr" can >> execute without a problem. However trying to use an existing >> python.exe (e.g. the standard installed one, but we also need to use >> it embedded) we always get the following error: >> >> ImportError: dynamic module does not define init function (initclr) >> >> What magic does the included python.exe perform, or what are we doing >> wrong in our installation. > > I got a reply to my bug report: > > https://bugzilla.novell.com/show_bug.cgi?id=334544#c4 > > --- Comment #4 from Paolo Molaro <[EMAIL PROTECTED]> 2007-10-19 00:40:09 > MST --- > ilasm doesn't support unmanaged exports, that is exporting managed > methods as unmanaged functions in a dll. This would be only useful on > windows as other systems don't use PE files for shared libraries, so > unless someone contributes the code this feature has no meaning in the > mono context. > > > Christian > > > > _________________________________________________ > Python.NET mailing list - PythonDotNet@python.org > http://mail.python.org/mailman/listinfo/pythondotnet -------------------------- Brian Lloyd [EMAIL PROTECTED] _________________________________________________ Python.NET mailing list - PythonDotNet@python.org http://mail.python.org/mailman/listinfo/pythondotnet
