Author cben
Recipients belopolsky, cben, eric.araujo, lesmana, loewis, ned.deily, pitrou, r.david.murray, ronaldoussoren
Date 2011-09-06.15:54:26
SpamBayes Score 2.08392e-07
Marked as misclassified No
Message-id <>
In-reply-to <1315320714.3617.7.camel@localhost.localdomain>
On Tue, Sep 6, 2011 at 17:54, Antoine Pitrou <> wrote:

It covers the user's desire customization very well (esp. if it worked with
sys.__interactivehook__ has the benefit of being cleanly settable from
python code.
But it might well be a YAGNI idea.

$PYTHONSTARTUP doesn't work with -i

Perhaps it should?
I can't think of a thing that makes sense in $PYTHONSTARTUP that I wouldn't
want with -i.
(and if there is one, one can add a test for sys.flags.interactive, or run
with env PYTHONSTARTUP='')

Point to watch out for: errors in $PYTHONSTARTUP.
One of the uses of "python -i" is doing on an exception
thrown by the script;
ideally a broken $PYTHONSTARTUP would not overr

"customization" than editing?
The fact that it'd be implemented in
Yes, obviously, if it's implemented in, -S should disable it.  My
point was that it doesn't have to be implemented there.  You could drink the
cool aid instead :-)
File name Uploaded
unnamed cben, 2011-09-06.15:54:25
Date User Action Args
2011-09-06 16:06:06eric.araujounlinkissue5845 messages
2011-09-06 15:54:27cbensetrecipients: + cben, loewis, ronaldoussoren, belopolsky, pitrou, ned.deily, eric.araujo, r.david.murray, lesmana
2011-09-06 15:54:26cbenlinkissue5845 messages
2011-09-06 15:54:26cbencreate