Re: [IronPython] Importing in a background thread

2008-11-21 Thread Dino Viehland
If you're getting crazy and are willing to experiment you could also look at IL rewriting compiled modules so they target Silverlight. In theory it's just updating what assembly name we're targeting. Maybe I've just not been following the Silverlight threads close enough but what do you mean b

[IronPython] Importing in a background thread

2008-11-21 Thread Dan Eloff
I'm curious why importing in a background thread fails completely in Silverlight (well anything builtin and anything already loaded works). There seems to be many ways of hacking together a crude working import function using exec, imp, or the hosting api. This would lead me to believe that there's

Re: [IronPython] Blocker: subclasses of float have trouble with __int__ and __str__

2008-11-21 Thread Dino Viehland
We're going to fix this bug a couple of others (in addition to the couple fixed in the current sources) and release an RC2. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glenn Jones Sent: Thursday, November 20, 2008 4:33 AM To: users@lists.ironpython.com Subject: [IronPython] Blo

Re: [IronPython] SystemExitException ?

2008-11-21 Thread Orestis Markou
Thanks! So we'll remove SystemExitException handling. Tomas Matousek wrote: It's handled for you in ExecuteProgram and the exit code is returned. It's this handling that makes the difference between Execute and ExecuteProgram. ExecuteProgram is designed to process any program exit mechanism th

Re: [IronPython] (ironclad) is it possible to get the current ScriptEngine?

2008-11-21 Thread William Reade
Thanks again Dino: it's all working and checked in, and it was all much easier than I expected. No problems with SourceUnits, but I don't try to do anything remotely complex with them, so others' mileage may vary. Dino Viehland wrote: Oh, and instead of ScriptSource you can use SourceUnit. Yo

Re: [IronPython] SystemExitException ?

2008-11-21 Thread Tomas Matousek
It's handled for you in ExecuteProgram and the exit code is returned. It's this handling that makes the difference between Execute and ExecuteProgram. ExecuteProgram is designed to process any program exit mechanism that the language has so that the host doesn't need to care and could be languag

[IronPython] SystemExitException ?

2008-11-21 Thread Orestis Markou
Hello, In Resolver, we have our own RSIronPython.exe that sets up the environment (PATH and other things) and executes a program. It's not interactive - just a wrapper aroung ExecuteProgram, really. We used to do this: try { ScriptSource source = engine.CreateScriptSourceFromFile(Path.C