In case someone wants to catch it before it's too late:
CallSiteBinder.Bind's returns comment: hte - the
J
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
1. You will need to deploy all the lib
* ipy.exe
* IronPython.dll
* IronPython.Modules.dll
* Microsoft.Scripting.Core.dll
* Microsoft.Scripting.dll
* Microsoft.Scripting.ExtensionAttribute.dll
The last three dlls are DLR which IP 2.0 relies on.
I never use ipy to deploy application so I'm not
Thanks Dody. The error was because I did not deploy Lib and the types module
is in Lib.
I can see that I can successfully deploy by copying the whole of IronPython.
It would be neater to turn the script(s) into an exe and deploy that.
I have only found IPy 1.0 doco on this and the 1.0 doco
Howland-Rose, Kyle wrote:
Thanks Dody. The error was because I did not deploy Lib and the types module
is in Lib.
The types module is part of the Python standard library - you only need
to deploy it if you use it.
You can compile your Python file and libraries into an executable /
Hello,
I tried reactivate parallel importing in Resolver One. More info in
this thread from October:
http://groups.google.com/group/ironpy/browse_thread/thread/11c5c917d716b7cc/58ce4e4260c2773a?lnk=gstq=parallel+import#58ce4e4260c2773a
I hit a problem. Sometimes during importing I get the
This is fixed in 2.6 and we can backport the fix to 2.0. Could you open a bug
on CodePlex? If you want to add the fix locally you just need to add the lock
statement below to NewTypeMaker.StoreOverriddenMethods:
lock(PythonTypeOps._functions) {
foreach (BuiltinFunction bf
