(actually, any non-string or non-bytes type).

fromlist which causes its own ImportError (e.g. the module tries to
import a non-existent module) should have that exception propagate.

fromlist of __import__ propagate.

The problem previously was that if something listed in fromlist didn't
exist then that's okay. The fix for that was too broad in terms of
catching ImportError.

The trick with the solution to this issue is that the proper
refactoring of import thanks to importlib doesn't allow for a way to
distinguish (portably) between an ImportError because finders couldn't
find a loader, or a loader raised the exception. In Python 3.4 the
hope is to introduce a new exception (e.g. ModuleNotFound) to make it
clean to differentiate why ImportError was raised.

This should make the Linux distros happy as it is now easier to leave
importlib's tests out of their base Python distribution.