Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Certify policyengine-us 2.15.17 in the US bundle

Ouverte
  • Quelque chose ne va pas ?
#538 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
42/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
python
Domaine
build-system, data

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Python
Étoiles
8
Forks
9
Merge moyen
15 h 28 min
PR mergées (30 j)
13

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de PolicyEngine/policyengine.py

Toutes les issues de PolicyEngine/policyengine.py

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.