Adopt required Python 3.11–3.14 support and record qualification
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Python
- Stelle
- 1
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di uibcdf/dockingmt
-
component:molsysmt
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
-
component:molsysmt component:molsysviewer
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
-
proposal
Difficoltà 4/5 3-5 giorni Idoneità per principianti 15/100
-
component:molsysmt
Difficoltà 5/5 Più di una settimana Idoneità per principianti 8/100
-
partial proposal
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
Tutte le issue di uibcdf/dockingmt
Issue simili
-
Add `openai_safety_identifier`, the replacement for the `user` field that `openai_user` sendsAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
pydantic/pydantic-ai#12091 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
Enhance blog readabilityApertaCSS enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
pychess/pychess-variants#2448 ·
I maintainer di solito rispondono entro 1 giorno
-
Bump locked PyTensor so Apple clang 21 does not pass -ld64Forse già presa @drbenvincent l’ha presa oggi. Apertabug dev ops
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 2 giorni
-
ai_p2 bug comp-datalake
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
ClickHouse/ClickHouse#128306 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno