[IPython-user] Killing a hung program

[Prabhu Ramachandran]

>>>>> "Fernando" == Fernando Perez <Fernando.Perez at colorado.edu> writes:

    >> 1. Allow the user to have one logfile that always logs stuff
    >>    into
    >> .ipython/log.  Unlike __IP.savehist, this log is always
    >> up-to-date.

    Fernando> Well, what do you do there with a user who is running
    Fernando> (as I often do) an ipython session in each of 5
    Fernando> concurrently open shells?  They are going to trample
    Fernando> each other pretty badly, no?

Hmm, yes, I do that too.  This is a pain.

    >>
    >> 2. An option to specify the log mode from the command line.
    >>    Right
    >> now you can say ipython -l, but that by default uses the rotate
    >> mode (which I dislike).  I ran into this problem sometime back
    >> but did not get the chance to post about it.

    Fernando> Yes, we could add a new command-line switch for this,
    Fernando> though I fear that ipython already has too many options
    Fernando> at the CL.  What about just having in your rc file a
    Fernando> call to %logstart in any way you like?  That's the
    Fernando> beauty of the rc file: you can set your ipython session
    Fernando> to behave _exactly_ the way you personally want it to,
    Fernando> with arbitrarily complex configurations, without
    Fernando> cluttering the public interface with too many details.

Maybe the rotate mode makes sense after all.

    Fernando> If anything, in the future (as the rc files become
    Fernando> regular python code) I'm inclined to have _less_
    Fernando> command-line options rather than more, and leave all
    Fernando> complex configuration to be done in the rc file.

Sounds fine, however, sometimes you have a default configuration and
want just one session to be a little different.  Having a command line
argument for this case is handy.

cheers,
prabhu