Repository navigation
docs: state Python 3.11 as the minimum after 0.9.111 - #5238
Deepanshu-Mehta wants to merge 1 commit into
Conversation
0.9.111 raised requires-python to >=3.11 (2b28033), but the README, its 31 translations and CONTRIBUTING still said 3.10+, so a 3.10 user following them silently resolves 0.9.110. Update those, the bug-report Python dropdown (drop 3.10, add 3.14 to match the CI matrix), the welcome bot's test advice and RELEASING's interpreter step, and point ruff's target-version and pyright's pythonVersion at 3.11. Ruff and pyright results are unchanged. The remaining 3.10 compatibility code (tomli markers and fallbacks) is left for a separate change, since dropping the markers touches uv.lock.
|
Thanks for the pull request, @Deepanshu-Mehta. A maintainer will review it soon. Want to talk it through while it is in review? Come join us on our Discord server. For longer-form discussion there is also GitHub Discussions. A couple of things that speed up review: make sure the test suite passes on Python 3.10 and 3.13, and that the change keeps extraction deterministic. |
There was a problem hiding this comment.
Graphify reviewed this change.
Worth a look — the grounded gate found no coupling regressions or blocking issues, but 1 advisory finding(s) below merit a look before merge.
Not checked: tests were not run; no formal proof of the changed code.
Graphify review — findings
Raises the documented minimum Python from 3.10 to 3.11 across the README, CONTRIBUTING, RELEASING steps, and every translated README, and moves the bug-report version picker to 3.11–3.14. The welcome bot and release checklist now name 3.11 and 3.13 as the interpreters to test on. Only docs and templates change, so requires-python in pyproject.toml and the ruff/pyright targets still describe the old floor until they are bumped to match.
Worth a look
- Tooling and docs moved to Python 3.11 but requires-python is not updated in this diff —
pyproject.toml:203· Escalate · medium- NOT verified (no proof, no reproducing execution) — needs human review
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 896 functions depend on the 896 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 896 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 896 function(s) in the blast radius were not formally verified this run
Test selection
Test selection
581 of 581 test file(s) selected (100%) via static blast radius.
Escalated to a full run for safety (
noncode-change,uncovered-code) — the selection is not trustworthy on its own (see below). CI should run the whole suite.
tests/pi.test.ts— full-run-safetytests/test_4874_jvm_resolution.py— full-run-safetytests/test_4909_reference_binding_scale.py— full-run-safetytests/test_4978_reconcile_cost.py— full-run-safetytests/test_4992_ts_import_types.py— full-run-safetytests/test_5072_splittable_under_cap_retry.py— full-run-safetytests/test_affected_cli.py— full-run-safetytests/test_affected_defines.py— full-run-safetytests/test_affected_member_seed.py— full-run-safetytests/test_affected_overrides.py— full-run-safetytests/test_affected_path_file_node.py— full-run-safetytests/test_affected_seed_reference_forms.py— full-run-safetytests/test_agents_platform.py— full-run-safetytests/test_alias_folding.py— full-run-safetytests/test_analyze.py— full-run-safetytests/test_anthropic_custom_endpoint.py— full-run-safetytests/test_antigravity_install.py— full-run-safetytests/test_apm_fallback_version.py— full-run-safetytests/test_architecture_doc.py— full-run-safetytests/test_astro_extraction.py— full-run-safetytests/test_astro_import_ids.py— full-run-safetytests/test_atomic_canvas_export.py— full-run-safetytests/test_atomic_version_stamp.py— full-run-safetytests/test_atomic_writes.py— full-run-safetytests/test_backend_env_isolation.py— full-run-safetytests/test_backend_extras.py— full-run-safetytests/test_backend_opt_in.py— full-run-safetytests/test_benchmark.py— full-run-safetytests/test_benchmark_raw_graph.py— full-run-safetytests/test_benchmark_real_query.py— full-run-safetytests/test_binary_media_words.py— full-run-safetytests/test_blade_extractor.py— full-run-safetytests/test_build.py— full-run-safetytests/test_build_located_semantic_identity.py— full-run-safetytests/test_build_merge_dedup_scope.py— full-run-safetytests/test_build_merge_ghost_fold_4955.py— full-run-safetytests/test_build_merge_hyperedges_and_prune.py— full-run-safetytests/test_build_merge_shrink_guard.py— full-run-safetytests/test_builtin_global_type_refs.py— full-run-safetytests/test_c_include_resolution.py— full-run-safetytests/test_cache.py— full-run-safetytests/test_cache_long_paths.py— full-run-safetytests/test_cache_stale_import_target.py— full-run-safetytests/test_cache_windows_case_4925.py— full-run-safetytests/test_callflow_html.py— full-run-safetytests/test_cargo_introspect.py— full-run-safetytests/test_cargo_missing_manifest.py— full-run-safetytests/test_carried_hyperedge_remap.py— full-run-safetytests/test_case_only_decl_ids_4904.py— full-run-safetytests/test_case_sensitive_resolution.py— full-run-safety- … and 531 more
non-code file(s) changed (
.github/ISSUE_TEMPLATE/bug_report.yml,.github/workflows/welcome.yml,CONTRIBUTING.md,README.md,RELEASING.md…) → running the full suite for safety (a code graph can't see config/fixture/data deps)
changed code file(s) with no mapped test (
.github/workflows/welcome.yml,CONTRIBUTING.md,README.md,RELEASING.md,docs/translations/README.ar-SA.md…) — a coverage gap or a missing link — running the full suite rather than only the selected tests
Selection is safe under the controlled-regression assumption; always-run tests + a periodic full run are the backstops. Advisory — it never changes the check verdict.
What does this PR do?
0.9.111 raised
requires-pythonto>=3.11(2b28033), but the user- and contributor-facing docs still say Python 3.10+. A 3.10 user who follows the README gets no error. Their install silently resolves 0.9.110, the last 3.10-compatible release.This PR updates every place that states the supported minimum:
README.md(Get started line and Prerequisites table) and the same two lines in all 31docs/translations/README.*.md(version number only)CONTRIBUTING.md"Python versions".github/ISSUE_TEMPLATE/bug_report.ymlPython dropdown: drop 3.10, add 3.14 to match the CI matrix (3.11–3.14).github/workflows/welcome.yml: the new-PR advice now says to test on 3.11 and 3.13 (string change only)RELEASING.mdstep 4: test on 3.11 and 3.13pyproject.toml:[tool.ruff] target-version = "py311",[tool.pyright] pythonVersion = "3.11"Type of change
Verification & Invariants
Docs are part of the behavior contract (CONTRIBUTING #14): the stated minimum should match
requires-python.3.10+with3.11+on the two requirement lines (62 lines changed, checked by diffing with the version masked).v8.uv lock --checkis clean.How was this tested?
Limitations
The leftover 3.10 compatibility code is not touched here: the
tomli; python_version < '3.11'markers inpyproject.toml, the tomli fallbacks incargo_introspect.py,manifest_ingest.py,tools/skillgen/gen.pyand some tests, and a few comments (paths.py,pyproject.toml:97). Removing the markers changesuv.lock, so that is a separate change.docs/superpowers/plans/andCHANGELOG.mdare historical and left as written.Graphify-specific checklist
--checkpasses)welcome.ymledit only changes a string literal)