Thanks Dino - no urgency for me. I usually compile DIE for my own use but under 2.6A1 it runs fairly snappily even when run from ipy :-)
Thanks, Davy On Tue, Mar 31, 2009 at 11:54 PM, Dino Viehland <[email protected]> wrote: > Yeah there is apparently an issue here, Resolver reported it to me the > other day off-line. We’ve been changing our code gen rather significantly > and it looks like our existing test coverage isn’t hitting whatever the > issue is here. I’ll probably look at it tomorrow. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Davy Mitchell > *Sent:* Tuesday, March 31, 2009 1:52 PM > *To:* Discussion of IronPython > *Subject:* [IronPython] PYC and 2.6 A1 > > > > Hi Guys, > > > > Are there known issues with PYC and IPY 2.6 A1? > > > > When my exe compiles, I get: > > > Unhandled Exception: Microsoft.Scripting.Runtime.UnboundNameException: name > 'ThreadExceptionEventArgs' is not defined > at Microsoft.Scripting.Actions.Calls.MethodTarget.Caller.Call(Object[] > args, Boolean& shouldOptimize) > at > IronPython.Runtime.Types.BuiltinFunction.BuiltinFunctionCaller`6.Call5(CallSite > site, CodeContext context, TFuncType func, T0 arg0, T1 arg1, T2 arg2, T3 > arg3, T4 arg4) > at > Microsoft.Scripting.UpdateDelegates.UpdateAndExecute7[T0,T1,T2,T3,T4,T5,T6,TRet](CallSite > site, T0 arg0, T1 arg1, T2 arg2, T3 arg3, T4 arg4, T5 arg5, T6 arg6) > at IronPython.Runtime.Importer.Import(CodeContext context, String > fullName, PythonTuple from, Int32 level) > at IronPython.Runtime.Operations.PythonOps.InitializeModule(Assembly > precompiled, String main, String[] references) > at PythonMain.Main() > > Works fine in 2.01. > > > > Thanks, > > Davy Mitchell > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > >
_______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
