Delete or repopulate empty projects/policyengine-api-full directory
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system, developer-experience
Research direction
Inspect the origin/main tree at projects/policyengine-api-full/ and compare the related context in issue #271 and the references to policyengine-api-v2-alpha and policyengine-api-simulation. Determine whether deletion or repopulation is intended, then verify that workspace discovery and the top-level README no longer describe a misleading project; done means the directory layout and related issue references are consistent.
Written by the indexing model from the issue text.
Description
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).
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 15h 3m
- Merged PRs (30d)
- 14
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PolicyEngine/policyengine-sim-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PolicyEngine/policyengine-sim-api#314 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PolicyEngine/policyengine-sim-api#685 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
PolicyEngine/policyengine-sim-api#679 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PolicyEngine/policyengine-sim-api#674 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PolicyEngine/policyengine-sim-api#646 ·
Maintainers usually reply within 2 days
All issues in PolicyEngine/policyengine-sim-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
521xueweihan/HelloGitHub#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sandialabs/atlas-ui-3#978 ·
Maintainers usually reply within 1 day
-
area: tests perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Nitjsefnie-Harness-Commons/daedalus#1255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4256 ·
Maintainers usually reply within 1 day