Bump (or relax) the policyengine-us pin — 1.729.0 is behind 1.742.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Search the package metadata for the us, models, and dev extras and locate the exact policyengine-us==1.729.0 pin. Review the packaging dependency constraints, update them to address compatibility with versions 1.742.0 and newer, then verify that the extras install without pip conflicts and retain the requested newer policy features.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Python
- Stars
- 8
- Forks
- 9
- Avg merge
- 15h 28m
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.py
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PolicyEngine/policyengine.py#549 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/policyengine.py#473 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/policyengine.py#408 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
PolicyEngine/policyengine.py#551 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
PolicyEngine/policyengine.py#543 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/policyengine.py
Similar issues
-
adr
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kristofdegrave/homeassistant-smart-charging#1607 ·
Maintainers usually reply within 1 day
-
namespace operations
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
EclipseFdn/open-vsx.org#13665 ·
Maintainers usually reply within 1 day
-
doc good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
collective/icalendar#1865 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
canonical/opentelemetry-collector-operator#409 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
mozilla/addons-release-tests#1243 ·
Maintainers usually reply within 1 day