Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Certify policyengine-us 2.15.17 in the US bundle

Abierto
  • ¿Algo no está bien?
#538 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
42/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
build-system, data

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Python
Estrellas
7
Forks
9
Merge medio
17 h 40 min
PR fusionados (30 d)
10

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PolicyEngine/policyengine.py

Todos los issues de PolicyEngine/policyengine.py

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.