Cherniavsky Beni <b...@google.com> added the comment:
On Tue, Sep 6, 2011 at 17:54, Antoine Pitrou <rep...@bugs.python.org> wrote:
It covers the user's desire customization very well (esp. if it worked with
-i).
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 script.py" is doing pdb.pm() 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 site.py?
Yes, obviously, if it's implemented in site.py, -S should disable it. My
point was that it doesn't have to be implemented there. You could drink the
cool aid instead :-)
----------
Added file: http://bugs.python.org/file23108/unnamed
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue5845>
_______________________________________
<div class="gmail_quote">On Tue, Sep 6, 2011 at 17:54, Antoine Pitrou <span
dir="ltr"><<a href="mailto:rep...@bugs.python.org";
target="_blank">rep...@bugs.python.org</a>></span> wrote:<br><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div><br><span style="color:rgb(34, 34, 34);font-family:arial,
sans-serif;font-size:14px">Ãric Araujo <<a href="mailto:mer...@netwok.org";
style="color:rgb(17, 85, 204)" target="_blank">mer...@netwok.org</a>> added
the comment:<br>
</span>
</div><div>> > It's more useful to have a hook called when entering
interactive mode, rather than a flag<br>
> > that's set from the beginning:<br>
> We already have such a hook: $PYTHONSTARTUP<br>
<br></div></blockquote><div>Good point!</div><div>It covers the user's
desire customization very well (esp. if it worked with
-i).</div><div>sys.__interactivehook__ has the benefit of being cleanly
settable from python code.</div>
<div>But it might well be a YAGNI idea.</div><div><br></div><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><div>
</div>$PYTHONSTARTUP doesn't work with
-i<br></blockquote><div>Â </div><div>Perhaps it should?</div><div>I can't
think of a thing that makes sense in $PYTHONSTARTUP that I wouldn't want
with -i.</div><div>(and if there is one, one can add a test
for sys.flags.interactive, or run with env PYTHONSTARTUP='')</div>
<div>Â </div><div>Point to watch out for: errors in
$PYTHONSTARTUP.</div><div>One of the uses of "python -i script.py" is
doing <a href="http://pdb.pm";>pdb.pm</a>() on an exception thrown by the
script;</div><div>
ideally a broken $PYTHONSTARTUP would not overr</div><div><br></div><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex"><div><div><div>> BTW, drawback of doing any such
setup in site.py: "python -S" would be unfriendly!People using -S
donât want the customizations done in site, so I donât think thereâs a
problem here.</div>
<div><br></div></div></div></blockquote><div>python -S doesn't disable
readline. Â What makes completions more of a "customization" than
editing?</div><div>The fact that it'd be implemented in site.py?</div>
<div>Yes, obviously, if it's implemented in site.py, -S should disable it.
 My point was that it doesn't have to be implemented there.  You could
drink the cool aid instead :-)</div></div>
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
