New submission from Dave Jones:
import subprocess hangs for ~25 seconds, 700+ files in dir - py 2.7.3, 2.6.6
I'm running this test from a LiveCD to make sure the environment is relatively
clean.
--
localhost Desktop # python --version
Python 2.7.3
--- works
Dave Jones added the comment:
That line (1) seems to pop up every time the subprocess call hangs
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17124
___
Dave Jones added the comment:
Distros tested with include Funduntu 2012-4, Fuduntu 2013-1, Fedora 17,
Scientific Linux 6.3 OpenSUSE 12.2 (all 32-bit) on the same hardware.
--
___
Python tracker rep...@bugs.python.org
Dave Jones added the comment:
I think I found something but I do not know what it means.
Everytime the import hangs, it seems to leave behind a time.pyc
There are only 29 files in this directory.
[jonesda0@linux-2py2 pycode]$ ls -1tr
py5.py*
py4.py*
py3.py*
py2.py*
py1.py*
print_func.py
test.py
Ian Cordasco added the comment:
As a further note, on python 2.6, I just touched a file called time.py, and in
the interpreter imported subprocess. It didn't hang because the file was empty
but it did generate a pyc file. This is almost certainly the root of your
problem. I doubt this is a
Ian Cordasco added the comment:
Could you give us the contents of your time.py file? I wonder if there's
something in that file that is causing the import to hang. It's the only reason
I can think of as to why the time.pyc file shows up.
Also, if you want to check before-hand, make a new
Dave Jones added the comment:
Hello Ian.
Thank you for the reply.
As I imagine you understand, I delete the time.pyc file every time it comes
back.
That being said, there *is* a time.py script in there from some testing I was
doing:
[jonesda0@toshiba pycode]$ ls -1tr *.py* | egrep sp|time
