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

Adopt required Python 3.11–3.14 support and record qualification

Abierto
  • ¿Algo no está bien?
#30 9 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
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, python
Área
ci-cd, release

Línea de trabajo

Start with devguide/pending_proposals/adopt_required_python_314.md and the cited CI runs and exact source checkpoints to understand the recorded qualification evidence. Review the central receipts in uibcdf/molsyssuite and identify component-owned blockers, applicable public artifacts, and independent clean-install evidence. Done means the remaining acceptance items are resolved or explicitly tracked and support claims align before admission; the issue says no public upload is performed here.

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

Descripción

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 004c2886d7d61ef2472656d437bddd5b87c2d74d 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 37107875583 at ff64d84239dbadd030ac1ba5f82eb0a60b5517b4 provides the recorded evidence. All four Linux minors pass CI at ff64d84. Full matrix 37108673271 at 0c48cf7 passes all six cells, including macOS ARM 3.13/3.14, ordinary installation, isolated metadata/import checks, interpreter/architecture and required Vina validation, followed by full tests. Concurrent score/ranking work and its guard correction were preserved. Public delivery and independent installation remain pending.

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 5 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 37109949389 passes, retains 1 skipped commit(s) after executed watermark 0c48cf73f5b1f89dc374d1628e3a0d0f7c547ca0 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 fda469f0200592720b75ea32b527e636a3797927 adopts immutable policy-v1.5.4 and the synchronized guide. Policy 37122607338 passes on exact source fda469f0200592720b75ea32b527e636a3797927 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
Python
Estrellas
1
Forks
0
Merge medio
30 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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/dockingmt

Todos los issues de uibcdf/dockingmt

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.