Unusual minidom behaviour: Part Deux

[Guido van Rossum]

"Victor Bazarov" <vAbazarov at dAnai.com> writes:

> "Guido van Rossum" <guido at python.org> wrote...
> > Martin von Loewis <loewis at informatik.hu-berlin.de> writes:
> >
> > > "Victor Bazarov" <vAbazarov at dAnai.com> writes:
> > > [...]
> >
> > The only situation where I've seen this, ironically, is if you attempt
> > to import the test module that's designed specifically to test this
> > lock, in the interactive interpreter on Windows.
> >
> > --Guido van Rossum (home page: http://www.python.org/~guido/)
> 
> I just saw something that might be relevant.  Please, don't jump
> the gun, I said "might".  The other thread ("Re: Threads in Python
> version 1.5, thread doesn't start until calling process dies") is
> discussing a problem with threads in Python.  The death of the
> calling process lets the system to go ahead.
> 
> It may or may not be relevant, but I would like to hear your
> opinion on it.
> 
> The big difference is that in the aforementioned posts the version
> of Python is 1.5.1 and I am using 2.0.

Victor, we don't have enough information.  Are you using Jython, or
are you somehow invoking C-Python from Java?  Can you reproduce the
problem in a self-contained example program?

--Guido van Rossum (home page: http://www.python.org/~guido/)