|
These are good suggstions. I have opened this bug (http://www.codeplex.com/WorkItem/View.aspx?ProjectName=IronPython&WorkItemId=1547) for it.
Since we locking down for V1, we are unlikely to fix this for V1. Please let us know if it is a critical issue for you.
________ Do you want to help develop Dynamic languages on CLR? (http://members.microsoft.com/careers/search/details.aspx?JobID=6D4754DE-11F0-45DF-8B78-DC1B43134038) From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kristof Wagemans
Is PythonEngine.Import() a hosting version of the python import statement? It behaves differently and not all features of import are (yet?) exposed. PythonEngine pe = new PythonEngine(); pe.LoadAssembly(Assembly.GetAssembly(typeof(System.Data.DataSet))); pe.Execute("import System.Data"); // Adds System to pe.Globals. This is what I would expect. pe.Import("System.Data"); // Adds Data to pe.Globals.
Is PythonEngine.LoadAssembly() a good name for the method? It seems to behave more like clr.AddReferenceXYZ then clr.LoadAssemblyXYZ. Also, clr.LoadAssembly loads and returns an assembly while PythonEngine.LoadAssembly() takes an assembly as parameter and returns nothing.
The following code fails silently. Wouldn’t it be better to throw an ImportError exception? PythonEngine pe = new PythonEngine(); pe.Import("DoesntExist");
|
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
