Re: missing for the top-level Python script

References	<CAPTjJmpVVfPzwrbeornk9Txyfiz+H5MDfHG2nY_9va7RCUEmEw@mail.gmail.com> <CAPTjJmrhz7crC2_x+ZN9sLgPvd8B1Yn8skzMSTBXJ6gSj55TqQ@mail.gmail.com> <CANc-5UybJQu+QgUrL-kS4XUH5iQHHuWJfaqDu-y00PcvszY5PQ@mail.gmail.com> <CAPTjJmrikcja8MbhgwmHvFDdgigQaHwsYo+tLR5q6OLfhPHcJQ@mail.gmail.com>
Date	2014-11-12 13:09 -0500
Subject	Re: __missing__ for the top-level Python script
From	Skip Montanaro <skip.montanaro@gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.15733.1415815796.18130.python-list@python.org> (permalink)

Show all headers | View raw

On Wed, Nov 12, 2014 at 12:49 PM, Chris Angelico <rosuav@gmail.com> wrote:
> Interesting data point there - that you actually have it handy and
> choose not to use it.

And, I believe I wrote it. Can't have a worse recommendation than
that. A cook who doesn't eat his own cooking. :-) I think I disabled
its import sometime in the distant past when it interacted badly with
something else, but for the life of me, I can't remember the details
anymore.

I will occasionally paste functions from Python source files into the
interactive interpreter. This autoload functionality can be kind of
handy there so you don't have to go back and also grab the imports
from the top of the source file.

Skip

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: __missing__ for the top-level Python script Skip Montanaro <skip.montanaro@gmail.com> - 2014-11-12 13:09 -0500

csiph-web