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

Adopt required Python 3.14 support and installed qualification

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

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start with devguide/pending_proposals/adopt_required_python_314.md and the referenced devguide/rollouts/policy154_routine_adoption.json, then inspect the linked CI runs and component issues. Done means the qualification blockers are resolved or explicitly tracked, applicable immutable public artifacts and independent clean-install evidence exist, and support claims are aligned before admission.

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

Descripción

component:lindelint component:molsysmt component:molsysviewer enhancement partial

Recorded source checkpoint — Adopt the required Python 3.11–3.14 contract under uibcdf/molsyssuite#51. Current published checkpoint 7f3e02840b15dde7891b196c76a6fdd617eedd90 declares >=3.11,<3.15 and calls immutable policy-v1.5.3. Source/full-CI, contributor guidance, applicable recipes and installed-candidate gates are aligned; the measured source snapshot used routine Python 3.13.

How — Source CI 37106324494 at 062d6347a142476067ffdb86c06c6cfd9478e51a provides the recorded evidence. Reporting governance and all four Python 3.13/3.14 cells pass. The four unchanged 3.11/3.12 cells retain the known trajectory-generation failure tracked under uibcdf/elastnetmt#14 and uibcdf/elastnetmt#17. The team owns that scientific work. Public noarch delivery remains under uibcdf/elastnetmt#18; the 3.14 route consumes LinDelINT's migration under uibcdf/lindelint#14.

Why — Requirement, tested source and public delivery are different claims. The suite records source feasibility as authorized, with public admitted delivery pending. The badge stays unchanged. Existing scientific assertions and older-minor dependency routes are preserved; the new 3.14 lanes use reviewed exact MolSysSuite providers rather than bypassing Requires-Python.

PR/recovery controls — Main retains strict protection with 11 checks including the new 3.14 route; previous checks and administrator direct-push bypass are preserved. Historical three-minor matrices cannot clear four-minor debt. Brief probe 37109920569 passes, retains 52 historical skipped commits without a passing four-minor watermark and decides full recovery is due. Heavy jobs were intentionally omitted by probe mode; this is not an executed recovery-suite claim.

Record — devguide/pending_proposals/adopt_required_python_314.md; central machine receipts are devguide/rollouts/python314_remaining_source_adoption.json in uibcdf/molsyssuite.

Acceptance still open — Resolve or explicitly track component-owned qualification blockers, produce applicable immutable public artifacts and independent public clean-install evidence, and align support claims before admission. No public upload is performed by this governance change. MolSysMT/MolSysViewer code and scientific suites are not changed or launched; they are dependency source consumers in the new lane.

Current policy deployment — Published commit 30ca342b53bb4236ced0b2b426786a507f939f22 adopts immutable policy-v1.5.4 and the synchronized guide. Policy 37122884152 passes on exact source 30ca342b53bb4236ced0b2b426786a507f939f22 with Python 3.14. Routine development is now 3.14; full matrices retain every supported minor. Central receipts: devguide/rollouts/policy154_routine_adoption.json under uibcdf/molsyssuite#39. The earlier 1.5.3 scientific source evidence above remains scoped to its recorded commits and closures; public delivery and remaining scientific qualification stay open.

Lenguaje dominante
Jupyter Notebook
Estrellas
4
Forks
3
Merge medio
9 h 40 min
PR fusionados (30 d)
2

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 uibcdf/elastnetmt

Todos los issues de uibcdf/elastnetmt

Issues similares

Más issues de Build System

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.