Problem
policyengine 4.18.2 pins policyengine-us==1.729.0 (exact, via the us/models/dev extras). That's well behind the current policyengine-us (1.742.0), and the exact pin means a downstream project can't install policyengine[us] alongside a newer policyengine-us — pip rejects the conflict.
Impact
The Child Poverty Impact Dashboard wants to adopt policyengine.py as its analytics framework, but depends on policyengine-us features newer than 1.729.0:
- Rhode Island CTC (1.731.0)
- SC dependent-exemption parameter (1.740.0)
- SC fully-refundable EITC contrib reform (1.741.0)
Adopting policyengine[us] today would regress those.
Ask
Bump the pinned policyengine-us to the latest (1.742.0), and ideally relax the exact == pin to a floor (>=) so downstream consumers can move ahead without waiting on a policyengine.py release each time. Happy to open a PR if useful.
🤖 Generated with Claude Code
Problem
policyengine4.18.2 pinspolicyengine-us==1.729.0(exact, via theus/models/devextras). That's well behind the currentpolicyengine-us(1.742.0), and the exact pin means a downstream project can't installpolicyengine[us]alongside a newerpolicyengine-us— pip rejects the conflict.Impact
The Child Poverty Impact Dashboard wants to adopt policyengine.py as its analytics framework, but depends on policyengine-us features newer than 1.729.0:
Adopting
policyengine[us]today would regress those.Ask
Bump the pinned
policyengine-usto the latest (1.742.0), and ideally relax the exact==pin to a floor (>=) so downstream consumers can move ahead without waiting on a policyengine.py release each time. Happy to open a PR if useful.🤖 Generated with Claude Code