[IronPython] importing on different threads

[Curt Hagenlocher]

On Thu, Aug 21, 2008 at 5:59 AM, Seo Sanghyeon <sanxiyn at gmail.com> wrote:
>
> No, IronPython is "worse" in that its importer is not locked. CPython has
> (in addition to Global Interpreter Lock, since imported module can be
> a C extension)
> a lock around its importer: see imp.acquire_lock and imp.release_lock. Since
> import can cause another import, this is a reentrant lock.

I see that we've implemented these functions, but I don't think
they're actually being used to guard an import.  I'll look into that.

--
Curt Hagenlocher
curt at hagenlocher.org