It is proposed to support __getattr__ and __dir__ function defined on modules to provide basic customization of module attribute access.
It is sometimes convenient to customize or otherwise have control over access to module attributes. A typical example is managing deprecation warnings. Typical workarounds are assigning __class__ of a module object to a custom subclass of types.ModuleType or replacing the sys.modules item with a custom wrapper instance. It would be convenient to simplify this procedure by recognizing __getattr__ defined directly in a module that would act like a normal __getattr__ method, except that it will be defined on module instances. For example:
Another widespread use case for __getattr__ would be lazy submodule imports. Consider a simple example:
There is a related proposal PEP 549 that proposes to support instance properties for a similar functionality. The difference is this PEP proposes a faster and simpler mechanism, but provides more basic customization. An additional motivation for this proposal is that PEP 484 already defines the use of module __getattr__ for this purpose in Python stub files, see PEP 484.
In addition, to allow modifying result of a dir() call on a module to show deprecated and other dynamically generated attributes, it is proposed to support module level __dir__ function. For example:
The __getattr__ function at the module level should accept one argument which is the name of an attribute and return the computed value or raise an AttributeError:
If an attribute is not found on a module object through the normal lookup (i.e. object.__getattribute__), then __getattr__ is searched in the module __dict__ before raising an AttributeError. If found, it is called with the attribute name and the result is returned. Looking up a name as a module global will bypass module __getattr__. This is intentional, otherwise calling __getattr__ for builtins will significantly harm performance.
The __dir__ function should accept no arguments, and return a list of strings that represents the names accessible on module:
If present, this function overrides the standard dir() search on a module.
The reference implementation for this PEP can be found in [2].
This PEP may break code that uses module level (global) names __getattr__ and __dir__. (But the language reference explicitly reserves all undocumented dunder names, and allows “breakage without warning”; see [3].) The performance implications of this PEP are minimal, since __getattr__ is called only for missing attributes.
Some tools that perform module attributes discovery might not expect __getattr__. This problem is not new however, since it is already possible to replace a module with a module subclass with overridden __getattr__ and __dir__, but with this PEP such problems can occur more often.
Note that the use of module __getattr__ requires care to keep the referred objects pickleable. For example, the __name__ attribute of a function should correspond to the name with which it is accessible via __getattr__:
One should be also careful to avoid recursion as one would do with a class level __getattr__.
To use a module global with triggering __getattr__ (for example if one wants to use a lazy loaded submodule) one can access it as:
or as:
Note that the latter sets the module attribute, thus __getattr__ will be called only once.
This document has been placed in the public domain.
Source: https://github.com/python/peps/blob/main/peps/pep-0562.rst
Last modified: 2025-02-01 08:55:40 UTC