Issue 27997: ImportError should be raised consistently from import machinery.

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/72184

classification

Title:	ImportError should be raised consistently from import machinery.
Type:	behavior	Stage:	test needed
Components:	Interpreter Core	Versions:	Python 3.6

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	barry, brett.cannon, eric.snow, ncoghlan
Priority:	normal	Keywords:

Created on 2016-09-07 03:35 by eric.snow, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg274742 - (view)	Author: Eric Snow (eric.snow) *	Date: 2016-09-07 03:35
As indicated by issue #16384, the import machinery is not consistent in raising ImportError. Some places in _bootstrap.py (and _bootstrap_external.py) raise ImportError and others make no effort to wrap errors that get encountered. I would expect the import machinery to always raise ImportError, except that errors coming from executing a module to stay unwrapped. I haven't had a chance yet to catalog the specific cases of inconsistency. Regardless, changing to be consistent would introduce backward compatibility. However, it should not be a big problem so I think we'd be okay (with an appropriate What's New entry).

msg274742 - (view)

Author: Eric Snow (eric.snow) * (Python committer)

Date: 2016-09-07 03:35

As indicated by issue #16384, the import machinery is not consistent in raising ImportError.  Some places in _bootstrap.py (and _bootstrap_external.py) raise ImportError and others make no effort to wrap errors that get encountered.  I would expect the import machinery to always raise ImportError, except that errors coming from executing a module to stay unwrapped.

I haven't had a chance yet to catalog the specific cases of inconsistency.  Regardless, changing to be consistent would introduce backward compatibility.  However, it should not be a big problem so I think we'd be okay (with an appropriate What's New entry).

History
Date	User	Action	Args
2022-04-11 14:58:35	admin	set	github: 72184
2016-09-07 05:30:02	barry	set	nosy: + barry
2016-09-07 03:35:32	eric.snow	create