Names that have been resolved are not consistently removed from sys.lazy_modules
@johnslavik 已经在做这个了。
开始于 2026年9月11日。
- 主要语言
- Python
- 星标
- 77.2k
- 派生
- 35.9k
- PR 合并指标
- PR 指标待抓取
描述
Bug report
Bug description:
I'm slightly hesitant to raise this because there's still discussion over what sys.lazy_modules should be. The documentation for sys.lazy_modules currently states:
When a lazily imported module is accessed for the first time, its name is removed from this set.
In at least two cases I'm aware of names are not being removed. Names may also not be modules, but I'd consider that a documentation issue while I believe the failure to remove names is a bug.
Names of modules that have previously been resolved will be re-added, but not removed when resolved again.
import sys
mods = sys.lazy_modules.copy()
def get_lazy():
return sorted(sys.lazy_modules - mods)
lazy import x # added
print(get_lazy())
x # removed
print(get_lazy())
lazy import x # added again
x # not removed
print(get_lazy())
['x']
[]
['x']
Here I think the issue is adding x back to sys.lazy_modules when it's already in sys.modules.
Names that are not modules are not removed:
import sys
mods = sys.lazy_modules.copy()
def get_lazy():
return sorted(sys.lazy_modules - mods)
lazy from x import X
print(get_lazy())
X
print(get_lazy()) # Should be empty
['x', 'x.X']
['x.X']
CPython versions tested on:
3.15, CPython main branch
Operating systems tested on:
No response
Linked PRs
- gh-157714
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。