Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Certify policyengine-us 2.15.17 in the US bundle

Aperta
  • Qualcosa non va?
#538 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
42/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
build-system, data

Direzione di ricerca

Read docs/engineering/skills/data-certification.md and inspect the certified release manifest and scripts/bundle.py. Start by auditing stored inputs, comparing population aggregates and running the test suite for the pinned versions. Done means the evidence supports compatibility, the 2.15.17 claim is appended, certification succeeds, and policyengine-core is bumped to 3.32.8.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

The certified US bundle in policyengine 6.1.2 pins policyengine-us==2.2.1 and policyengine-core==3.32.5. The newest policyengine-us on PyPI is 2.15.17, which requires policyengine-core>=3.32.8.

2.2.1 still has SNAP rounding defects that later releases fix. PolicyBench recomputed its 1,984 US household reference outputs (tax year 2026) under both versions:

  • 22 outputs disagree: 13 SNAP, 8 federal_income_tax_before_refundable_credits and 1 state income tax.
  • Under 2.2.1, 12 of 19 positive annual SNAP amounts are not whole dollars. One NJ household gets 15,309.53 under 2.2.1 and 15,273 under 2.15.17.
  • Under 2.15.17, all 18 positive SNAP amounts are whole dollars.

PolicyBench records whether its reference model matches the policyengine.py certified bundle. Until policyengine.py certifies a current policyengine-us, every reference it builds on the newest model is flagged as uncertified.

Constraint

The certified data release populace-us-2024-spm-20260915 was built with policyengine-us 2.2.1. Its release manifest's publisher claim covers >=2.0.0,<2.3. Under the certification gate (docs/engineering/skills/data-certification.md), 2.15.17 needs either a new data build or a published compatibility claim for it.

Plan

  1. Build the evidence that the certified H5 means the same thing to 2.15.17 as to 2.2.1:
    • stored-input audit, covering renamed, removed and now-computed inputs and enum members;
    • population aggregates under both versions, with every move explained;
    • the test suite on the pinned pair.
  2. If the evidence holds, append a policyengine-us==2.15.17 claim to the release manifest, as #491 and #536 did for UK.
  3. Certify with scripts/bundle.py certify-data --country us --data-producer populace --model-version 2.15.17, and bump policyengine-core to 3.32.8.
Lingua principale
Python
Stelle
8
Fork
10
Merge medio
18h 24m
PR unite (30g)
18

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PolicyEngine/policyengine.py

Tutte le issue di PolicyEngine/policyengine.py

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.