[IronPython] Importing in a background thread
dinov at microsoft.com
Sat Nov 22 04:09:44 CET 2008
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?
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] 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
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.
Users mailing list
Users at lists.ironpython.com
More information about the Ironpython-users