Good to see some feedback, comments inlined. Should see a new post of my 2.0 release with some fixes today including just a binary release.
On 2/20/06, T Barket <[EMAIL PROTECTED]> wrote: > Hello, > > 1) the PythonNet2.0-0.1.zip file didn't include a file called "clrmodule.il" > but I substituted with the original one from Brian's > pythonnet-1.0-rc2-py2.4-clr1.1-src.zip Woops, not sure how that got left out :) > > 2) Then everything compiled and linked just fine. TestPython.exe worked > fine and the Python.exe launched and I could do "import CLR" and "import > CLR.System". However, I could not "import CLR.System.Windows" or "import > CLR.System.Drawing": [SNIP[ > > 3) This problem is bc in .Net 2.0, > System.Reflection.Assembly.LoadWithPartialName is now supposed to be > obsolete (http://msdn2.microsoft.com/en-us/library/0a7zy9z5.aspx). And I > I've added some additional code, but I'm not happy going back to a depricated API as we need a correct solution. Thew loader code will try and locate the assembly in the installed .NET Framework directory if Load() fails. This does not solve loading assemblies in the GAC, but there is no doubt a way to toss that in. I'll investigate in the next week or so and see if I can't locate a current rev. > 4) With the changes so far, I was able to use the PythonNet2.0 generated > Python.exe with no problems. However, i wasnt able to use clr.dll and > python.runtime.dll with a standard cpython interpretter, such as > c:/python24/python.exe, winpython or ipython which i was albe to do with > PythonNet 1.0. Correct me if I'm wrong, but I don't think this was an origional intended feature. > > 5) To fix (4), i made two changes to Michael's project (which i suspect go > back to Brian's original code). I commented out the code that performs the > import hook replacement in pythonengine.InitEx(): I'm sure we can get the importing to work right, but not a project for today. I recommend just using the .NET console version. Shouldn't be any issues there. > > 6) Brian, as a personal note, i would strongly encourage you to keep going > with Python for .Net regardless of IronPython. I personally have alot of If anything else we can move the code over to source forge to continue development. mike _________________________________________________ Python.NET mailing list - PythonDotNet@python.org http://mail.python.org/mailman/listinfo/pythondotnet
