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 by "if __import__ works"? And how does importing in a background thread fail? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Eloff Sent: Friday, November 21, 2008 7:02 PM To: Discussion of IronPython Subject: [IronPython] Importing in a background thread 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 nothing blocking import from working in threads on Silverlight. I've been hacking all day with Kamil's parallel importer, and using some crude hacks, I've managed to get quite far with it. Most every obstacle being an incompatibility between my import function and Python import semantics (which are not simple, especially with regard to nested packages!) So I've given up for now, but I'd like to be able to revisit this later if __import__ works. There seems to be no other optimization I can do that would give as much speedup to load time. -Dan _______________________________________________ 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
