Re: odd runtime error
- From: Chris Rebert <clp2@xxxxxxxxxxxx>
- Date: Wed, 1 Dec 2010 16:59:19 -0800
On Wed, Dec 1, 2010 at 4:49 PM, David Brown <dmlb2000@xxxxxxxxx> wrote:
So I'm not subscribed to python-list but would like to get an answer
to my question. I've made a small test program that dumps a
RuntimeError and I'd like to know why.
$ python test2.py
doing stuff
Traceback (most recent call last):
File "test2.py", line 3, in <module>
import test
RuntimeError: not holding the import lock
child 3693 exited with 256
$
Here's the setup, there's two files test.py and test2.py
$ cat test.py
#!/usr/bin/python
import os, sys
if os.fork() == 0:
print "doing stuff"
sys.exit()
print "child %d exited with %d" % os.wait()
It's *quite* strange for a module that's being imported to execute a
fork() in its body; this is almost assuredly the cause of the
RuntimeError. Why are you fork()ing in an importable module in the
first place?
Cheers,
Chris
--
http://blog.rebertia.com
.
- Prev by Date: odd runtime error
- Next by Date: Re: odd runtime error
- Previous by thread: odd runtime error
- Next by thread: Re: odd runtime error
- Index(es):
Relevant Pages
|
