Delete or repopulate empty projects/policyengine-api-full directory
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 重构
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- python
调研方向
检查 projects/policyengine-api-full/ 中的 origin/main 树，并对比 issue #271 中的相关上下文以及对 policyengine-api-v2-alpha 和 policyengine-api-simulation 的引用。确定预期是删除还是重新填充，然后验证 workspace 发现机制和顶层 README 不再描述一个具有误导性的项目；当目录布局和相关 issue 引用一致时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Summary
projects/policyengine-api-full/ on origin/main contains only uv.lock — no source, no pyproject.toml, no package directory. The tree is effectively abandoned.
What goes wrong
$ git ls-tree -r --name-only origin/main -- projects/policyengine-api-full
projects/policyengine-api-full/uv.lock
A lone uv.lock with no pyproject.toml or package content:
- Pins dependencies nothing can consume, so it drifts out of sync with reality on every
uvbump without anyone noticing. - Confuses readers — the directory name suggests a "full" sibling of
policyengine-api-simulation, but there's nothing there. - Breaks workspace-wide commands (pyright, ruff, pytest) that try to discover projects via directory structure.
Related: #271 (pyright broken on full API) implicitly references this tree but frames the problem around type-checking rather than emptiness.
Suggested fix
Pick one:
- Delete the directory if the full API has moved to
policyengine-api-v2-alpha(which appears to be the active direction based on #83 "Simulation/Report V2 Migration Foundation"). Most honest option — close #271 as no-longer-applicable. - Repopulate with a real
pyproject.toml+ package if the intent was to keep the non-simulation endpoints alive in this monorepo. Revisit #271 after.
A note in the top-level README explaining the monorepo layout (simulation lives here, full API lives elsewhere) would also reduce confusion for new contributors.
Severity
Low / tech-debt — doesn't break anything, but decays over time and confuses contributors.
Relates to
#271 (pyright on full API).
- 主要语言
- Python
- 星标
- 1
- 派生
- 1
- 平均合并
- 15 小时 3 分钟
- 30 天内合并 PR
- 14
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PolicyEngine/policyengine-sim-api 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
PolicyEngine/policyengine-sim-api#314 ·
维护者通常 2 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
PolicyEngine/policyengine-sim-api#685 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
PolicyEngine/policyengine-sim-api#679 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
PolicyEngine/policyengine-sim-api#674 · 3 条评论 ·
维护者通常 2 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
PolicyEngine/policyengine-sim-api#646 ·
维护者通常 2 天内回复
查看 PolicyEngine/policyengine-sim-api 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
521xueweihan/HelloGitHub#3790 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
sandialabs/atlas-ui-3#978 ·
维护者通常 1 天内回复
-
area: tests perceived difficulty: 2
难度 2/5 1-3 小时 新手友好度 72/100
Nitjsefnie-Harness-Commons/daedalus#1255 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
EleutherAI/lm-evaluation-harness#4256 ·
维护者通常 1 天内回复