Remove transitional cache access after country migrations
维护者通常 2 天内回复
还没有人认领这个 Issue。
- #603 来自 @anth-volk —— 已关闭，未合并
评估
调研方向
Start with draft PR #603 and the preparatory Core work in #599, tracked by #598, to identify the cache adapters, recovery paths, and compatibility mechanisms in scope; the issue names no files or tests. Read the country migrations in PolicyEngine/policyengine-us#9980 and PolicyEngine/policyengine-uk#2176, then validate against their released packages after all stated prerequisites are met. Done means the compatibility mechanisms are removed, replacements and the break are documented, and the required unit and migrated-path tests pass.
由索引模型根据 Issue 内容生成。
描述
Purpose
Remove transitional Core cache access after the public ownership APIs and their
guarantees have shipped and both country packages have migrated.
Implementation: draft #603. Keep it dependent on the releases below; creating
the draft does not satisfy the merge prerequisites.
This is the last stage of a three-stage, four-PR sequence:
- Preparatory Core: #599, tracked by #598.
- Country migrations: PolicyEngine/policyengine-us#9980 and
PolicyEngine/policyengine-uk#2176. - This Core cleanup, in a separate dependent draft PR.
Prerequisites before merge
- Publish the preparatory Core release.
- Update both country minimum Core dependencies and lockfiles to that release.
- Validate, merge, and publish both country migrations.
- Validate this cleanup against those released country packages.
Source-checkout tests can support development before release, but do not satisfy
released-package validation. Do not invent future package version numbers.
Scope
- Remove dictionary/set assignment adapters and recovery from legacy cache fields.
- Expose read-only cache observations, with mutations through typed operations.
- Reject removed writes instead of silently creating unused shadow attributes.
- Remove Core's remaining dependence on those compatibility mechanisms.
- Document supported replacements and the intentional compatibility break.
- Add at least 40 meaningful unit cases per production commit and test migrated
country paths without the removed mechanisms.
Preserve immutable entry sharing, authoritative supplied inputs, independent
branch snapshots, explicit policy sharing, revision-based invalidation, public
constructors, and public eager/lazy parameter configuration.
Phase 7 model-definition separation and persistent cache redesign are excluded.
- 主要语言
- Python
- 星标
- 22
- 派生
- 30
- 平均合并
- 2 天 21 小时
- 30 天内合并 PR
- 24
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-core 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
PolicyEngine/policyengine-core#605 · 1 条评论 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
PolicyEngine/policyengine-core#549 ·
维护者通常 2 天内回复
-
`restore_simulation` silently drops memberless group entities可能已有人在做 @Adelagric 于 31 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
PolicyEngine/policyengine-core#547 ·
维护者通常 2 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
PolicyEngine/policyengine-core#609 ·
维护者通常 2 天内回复
-
Every new system compiles its variable files again, which sys.monitoring coverage retains可能已有人在做 @MaxGhenis 今天认领。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
PolicyEngine/policyengine-core#607 ·
维护者通常 2 天内回复
查看 PolicyEngine/policyengine-core 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
KalicoCrew/kalico#1012 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
esphome/esphome.io#7657 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
VNG-Realisatie/gemma-zaken#2658 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
comp/gateway comp/plugins duplicate P3 type/bug
难度 2/5 1-3 小时 新手友好度 82/100
NousResearch/hermes-agent#137019 ·
维护者通常 1 天内回复