+1 from me. The interactive uses would be great, and aren't really nice to implement without a hook like this.

Top-posted from my Windows Phone

From: Chris Angelico
Sent: ý12/ý28/ý2014 10:42
To: python-ideas
Subject: [Python-ideas] Python hook just before NameError

I mainly did up this patch to see how hard it would be, and now it's
turned out to be fairly simple, I'm curious as to whether it would
actually be useful to people.

At the point where a global/builtin name lookup is about to raise
NameError, first try calling a Python function, along the same lines
as __getattr__. If that function hasn't been defined, raise NameError
as normal; but if it has, let it either raise NameError or return some
object, which is then used as if the name had been bound to it.

Patch is here:
http://bugs.python.org/issue23126

The idea is to allow convenient interactive use; auto-importing
modules is easy, and importing names from modules ("exp" --> math.exp)
can be done easily enough too, given a list of modules to try.

It's probably not a good idea to use this in application code, and I
definitely wouldn't encourage it in library code, but it has its uses
interactively.

Thoughts?

ChrisA
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/