[issue1255] Strange Python hangup

[Jiri Krivanek]

Jiri Krivanek added the comment:

The reason for it is pragmatic: The whole of my application is published
as .pyc files. Except of the only one which must stay .py - that one
which has to be executable (+x) on Linux and thus it starts with the line:
# !/usr/bin/python
and then it should only contain:
import <something>
and <something> is .pyc.

So I did a simple change into my application. I start it via a very
brief script whic only contains:
# !/usr/bin/python
import <something>

Wow! It stopped working at all!

After 4 hours of isolating of the problem I developped an elementary
code which demonstrates my problem (attached at the bug report).

I expect that the import statement does not return the control until the
code being executed by it finishes, does'n it?

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1255>
__________________________________