> you say "do this once", but actually it's "do it in each interactive > session again and again", ... That's what your Python startup file is for. I have been running with several tweaked builtin functions for years. Never have to consciously load them. If I wanted execfile badly enough, I'd define it there. I don't think I've used execfile more than a handful of times in the 20-odd years I've been using Python. Perhaps our personal approaches to executing code at the interpreter prompt are radically different, but I think if the lack of execfile is such a big deal for you, you might want to check around to see how other people use interactive mode. Skip -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140614/e697b64f/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4