in future please try to reply on-list, not to the person you're replying
to directly.
On 06/08/2010 03:00 PM, Alan wrote:
> Well, using code.interact() didn't help much.
>
> The problem is that one of the reasons (if not the main reason) of
> using 'python -i' is to be able to follow the simulatio
On 06/07/2010 01:43 PM, Alan wrote:
> Hi there,
>
> I have a code with a 'exit()' at the end. We run it usually as:
>
> python2.5 -i code.py
>
> and if everything is fine, the 'exit()' is called and there's no
> interactive terminal.
You could instead do something like this:
try:
# ...
except:
Hi there,
I have a code with a 'exit()' at the end. We run it usually as:
python2.5 -i code.py
and if everything is fine, the 'exit()' is called and there's no interactive
terminal.
However, doing the same above with python2.6 and I got:
amadeus[2738]:~/TMP% python2.6 -i thread_ping.py
Traceba
