Adopt required Python 3.11–3.14 support and record qualification
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 30m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uibcdf/dockingmt
-
proposal
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
component:molsysmt
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
partial proposal
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
component:molsysmt enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
proposal
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in uibcdf/dockingmt
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
huggingface/sentence-transformers#4186 ·
Maintainers usually reply within 5 days
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
QuantEcon/QuantEcon.py#988 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fabriziosalmi/certmate#1247 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 Half a day Newbie friendliness 72/100
sujithputta02/Esapay#13 ·