The proposed PR makes the following changes in sys.breakpointhook():

* Use _PyObject_GetBuiltin() for getting a builtin. This simplifies the code.

* The only effect of using the "from" list is when the imported name is a submodule. But it should be a callable. Callable module is very rare bird, I don't think we need to support such weird case. Removing the "from" list simplifies the code.

* Only ImportError and AttributeError raised from import are ignored. Other errors are exposed to the user as is. This is most likely a KeyboardInterrupt or MemoryError. They shouldn't be silenced.

sys.breakpointhook() was added in issue31353.

Hi Serhiy.  I'm curious whether this is a pure clean up or if there are actual problems you're trying to fix.

* I'm okay with using _PyObject_GetBuiltin() but it does bother me in general to use too many non-public (and thus undocumented) APIs.  It makes understanding what's going on more difficult.  This is a general gripe of mine with Python's C API.

* Given that removing support for callable modules is technically a backward incompatible change, is it worth it?  If we had done it before 3.7 was released, it would have been fine, but now we can't guarantee it won't break someone's code.  I agree it's unlikely, but it is possible.

* Perhaps we should explicitly pass through KeyboardInterrupt and MemoryError rather than just ignoring ImportError and AttributeError.

This is a pure clean up except the last item which fixes a minor problem. I had wrote this patch a while ago (perhaps before 3.7.0 was released), and now revive my old patches.

I think that the general rule is that exceptions shouldn't be ignored blindly, except in case when we have no choice (like in destructors). ImportError and AttributeError are expected exceptions raised in PyImport_ImportModuleLevelObject and PyObject_GetAttrString when PYTHONBREAKPOINT points to non-existing name, all other exceptions mean exceptional situation or programming error. Note that exceptions raised when call the hook are not ignored.

I will drop cleanup changes if they don't look good to you.

New changeset 6fe9c446f8302553952f63fc6d96be4dfa48ceba by Serhiy Storchaka in branch 'master':
bpo-34756: Silence only ImportError and AttributeError in sys.breakpointhook(). (GH-9457)
https://github.com/python/cpython/commit/6fe9c446f8302553952f63fc6d96be4dfa48ceba

The part of the clean up was applied in PR 9519. And since _PyObject_GetBuiltin() was gone, the rest of the clean up no longer applicable. The only part that is left is to make unexpected exceptions no longer silenced.

New changeset 6d0254bae4d739b487fcaa76705a2d309bce8e75 by Miss Islington (bot) in branch '3.7':
bpo-34756: Silence only ImportError and AttributeError in sys.breakpointhook(). (GH-9457)
https://github.com/python/cpython/commit/6d0254bae4d739b487fcaa76705a2d309bce8e75

I reopen the issue. This change broke test_builtin: see bpo-35742.

I can reproduce the test failure on my Fedoea 29 using:

./python -m test -v test_builtin -m TestBreakpoint

New changeset 3607ef43c4a1a24d44f39ff54a77fc0af5bfa09a by Serhiy Storchaka in branch 'master':
bpo-35742: Fix test_envar_unimportable in test_builtin. (GH-11561)
https://github.com/python/cpython/commit/3607ef43c4a1a24d44f39ff54a77fc0af5bfa09a

New changeset 97d6a56d9d169f35cf2a24d62bf15adfc42fc672 by Miss Islington (bot) in branch '3.7':
bpo-35742: Fix test_envar_unimportable in test_builtin. (GH-11561)
https://github.com/python/cpython/commit/97d6a56d9d169f35cf2a24d62bf15adfc42fc672