Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Globals read only inside a class body defined in a by-value function are not pickled (NameError after loading)

未关闭
#609 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 9 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
python
领域
backend

调研方向

Start by reading _extract_code_globals around GLOBAL_OPS in cloudpickle/cloudpickle.py, then inspect _function_getstate and the base_globals path in _function_getnewargs identified in the issue. Reproduce the provided example and check the related class-scope opcode cases across the listed Python versions. Done means the globals used by those class scopes are available after loading, with regression tests covering the reported cases.

由索引模型根据 Issue 内容生成。

描述

🤖 AI text below 🤖

A global that a by-value function reads only inside the body of a class it defines is not pickled, so the loaded function raises NameError. This happens on Python 3.11 through 3.14, with cloudpickle 3.1.2 and with master (4af5936).

import subprocess, sys
import cloudpickle

ns = {"__name__": "not_importable", "CONST": 42}  # not importable, so f is pickled by value
exec("def f():\n    class Rec:\n        q = CONST\n    return Rec.q\n", ns)
print("local:", ns["f"]())
load = "import pickle, sys; print(pickle.loads(sys.stdin.buffer.read())())"
r = subprocess.run([sys.executable, "-c", load], input=cloudpickle.dumps(ns["f"]), capture_output=True)
print("loaded:", (r.stdout or r.stderr).decode().strip().splitlines()[-1])

Output on 3.11.15, 3.12.10, 3.13.3 and 3.14.6:

local: 42
loaded: NameError: name 'CONST' is not defined

Other class-scope reads fail the same way:

  • a field annotation naming a global, for example a dataclass p: Point defined inside the function (measured on 3.13 and 3.14);
  • a class-scoped type Inner = G alias, once its value is evaluated (measured on 3.12, 3.13 and 3.14).

Cause: _extract_code_globals only collects names from GLOBAL_OPS, which is STORE_GLOBAL, DELETE_GLOBAL and LOAD_GLOBAL (L388-L397). Inside a class scope, the compiler reads names with other opcodes (measured with dis):

  • class-body statements, and annotations before 3.14, use LOAD_NAME (3.11-3.14);
  • a class's __annotate__ function (3.14) and a class-scoped type alias value (3.12+) use LOAD_FROM_DICT_OR_GLOBALS.

Suggested fix: add LOAD_NAME to GLOBAL_OPS, and also LOAD_FROM_DICT_OR_GLOBALS on 3.12+. Both consumers already keep only names present in func.__globals__, so class-local names collected this way are dropped:

Related: #608.

主要语言
Python
星标
1.9k
派生
206
平均合并
1 天 10 小时
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

cloudpipe/cloudpickle 的其他 Issue

查看 cloudpipe/cloudpickle 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。