Problem: Terminal (OS X) window exits immediately on opening. & Solution.

Python python at
Tue Mar 17 09:44:52 CET 2009

On 16 mrt 2009, at 22:15, Lou Pecora wrote:

> In article <mailman.1980.1237237525.11746.python-list at>,
> Python <python at> wrote:
>>> --
>> why don't you just execute the script directly form the terminal?
>> then you will be able to read all error messages...
>> and you can delete all the files you want
>> just my 2c
>> Arno
> Because the shell process in the Terminal window would exit right  
> after
> it started even when I was just trying to open a new window (not even
> running a script), i.e. command-N in Terminal.  So I could not run
> anything from the Terminal.
> More info:  There is an Executestring in the Terminal preferences that
> is executed (I would guess as a shell command or script) when the  
> shell
> starts up (which happens whenever a new window is opened).  If that is
> bad in any way, the shell exists with an error message.  There is no  
> way
> to run any shell in the Terminal at that point.  The only option  
> appears
> to be to clean up the preferences.  I don't know why the preferences  
> got
> a bad command while I was running Python scripts.  Maybe nothing to do
> with Python, maybe it does.  Not sure.
> -- 
> -- Lou Pecora
> --
oh i think it understand i now... it has nothing to do with python,  
has it?
just with some garbage left by a python script that should have been
deleted at startup of OSX

501 is the default user ID in OSX
maybe it's a bash thing?

More information about the Python-list mailing list