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.

Title: Raise ValueError when __loader__ not defined for importlib.find_loader()
Type: behavior Stage: test needed
Components: Library (Lib) Versions: Python 3.3, Python 3.4
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: brett.cannon Nosy List: Ankur.Ankan, asvetlov, barry, brett.cannon, eric.snow, gkcn, ncoghlan, python-dev, theller
Priority: normal Keywords: easy

Created on 2013-02-01 13:44 by brett.cannon, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg181079 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2013-02-01 13:44
If __loader__ is None then ValueError is raised, but if it is not defined then AttributeError is raised instead. Probably should harmonize around ValueError even in the missing attribute case since __loader__ = None is equivalent to the attribute not existing.

I'm on the fence about considering this a bug, though, since the docs say if __loader__ == None then ValueError but does not directly mention what happens if the attribute is missing. Since anyone who has written code for this probably is catching both attributes (if at all since all but three modules coming from Python will have __loader__ defined ATM), it should be fine, but it is still a change in API/semantics that doesn't contradict the docs.
msg181084 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2013-02-01 16:24
Should mention that this is probably no harder than changing a key getattr() call to None (as pointed out by Nick).
msg181356 - (view) Author: Eric Snow (eric.snow) * (Python committer) Date: 2013-02-04 17:49
My vote is for making this a ValueError in both cases (and amending the doc appropriately as well).  The error amounts to the same thing: the module did not have loader (implicitly or explicitly).  If someone wants to distinguish between the two they can explicitly check __loader__ on the module.

Incidently, _find_and_load_unlocked() has similar code to find_loader() (Lib/importlib/_bootstrap:1523) and raises ImportError instead of ValueError.  That's actually fine since it's a different situation.  However, _find_module() does not handle when __loader__ does not exist, so you would get neither ValueError nor ImportError.  I expect we'd want it or _find_and_load_unlocked() to convert the AttributeError into ImportError to be consistent both with the fix for this issue and with how we handle the __loader__ == None case there.


For reference, here is the original python-dev thread:

The reference to ValueError is in the importlib docs:
msg184097 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2013-03-13 18:09
New changeset cee04627bdd0 by Brett Cannon in branch 'default':
Issue #17099: Have importlib.find_loader() raise ValueError when
msg184098 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2013-03-13 18:11
I decided not to backport since it shifts what exception is raised.
Date User Action Args
2022-04-11 14:57:41adminsetgithub: 61301
2013-03-13 18:11:19brett.cannonsetstatus: open -> closed
resolution: fixed
messages: + msg184098
2013-03-13 18:09:57python-devsetnosy: + python-dev
messages: + msg184097
2013-02-23 17:27:55gkcnsetnosy: + gkcn
2013-02-19 14:42:49Ankur.Ankansetnosy: + Ankur.Ankan
2013-02-04 17:49:58eric.snowsetmessages: + msg181356
2013-02-03 16:50:00brett.cannonsetassignee: brett.cannon
2013-02-03 16:48:10brett.cannonlinkissue17115 dependencies
2013-02-01 19:15:51eric.snowsetnosy: + eric.snow
2013-02-01 16:24:35brett.cannonsetkeywords: + easy
2013-02-01 16:24:30brett.cannonsetmessages: + msg181084
2013-02-01 15:17:22barrysetnosy: + barry
2013-02-01 14:07:23asvetlovsetnosy: + asvetlov
2013-02-01 13:44:37brett.cannoncreate