Skip to content

ci: raise workspace runtimes to Python 3.12 #125

Description

@Jammy2211

Overview

Complete Phase 5B of the ecosystem Python 3.12 migration by raising the deployment runtime selector in the three user workspaces and three HowTo repositories. This is a coordinated six-line metadata change; it is intentionally held as one batch until every target repository is free.

Plan

  • Change all six root runtime.txt files to exactly python-3.12.1.
  • Preserve a terminating newline in each file.
  • Make no script, notebook, dependency, documentation, or workflow changes.
  • Validate the six exact values and git diff --check; do not repeat ecosystem tests for deployment-selector lines.
Detailed implementation plan

Affected Repositories

  • autofit_workspace (primary)
  • autogalaxy_workspace
  • autolens_workspace
  • HowToFit
  • HowToGalaxy
  • HowToLens

Branch Survey

Repository Current Branch Dirty? Current runtime
./autofit_workspace main clean python-3.10
./autogalaxy_workspace main clean python-3.11
./autolens_workspace main clean python-3.11
./HowToFit main clean python-3.11
./HowToGalaxy main clean python-3.11
./HowToLens main clean python-3.11

Suggested branch: feature/python-312-workspace-runtime-pins

Implementation Steps

  1. Wait for extra-galaxies-multi-galaxy to release its active autogalaxy_workspace claim; do not split the batch or overlap that task.
  2. Create one task worktree containing all six repositories from their current origin/main heads.
  3. Replace each root runtime.txt content with python-3.12.1 plus a newline.
  4. Verify all six exact values and run git diff --check in each repository.
  5. Open one pending-release PR per repository under the same task branch.

Key Files

  • autofit_workspace/runtime.txt
  • autogalaxy_workspace/runtime.txt
  • autolens_workspace/runtime.txt
  • HowToFit/runtime.txt
  • HowToGalaxy/runtime.txt
  • HowToLens/runtime.txt

Sizing Decision

The Feature Agent scored this too-large solely from six-repository and migration/test keywords. That proxy is overridden: the implementation is six identical one-line metadata edits with no API, script, notebook, or generated-artifact impact.

Original Prompt

Click to expand starting prompt

Ok, lets remove support for anything below python3.12, do a census to make sure we simplify requriements, build server, testing, etc. Also make sure all docs are updated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions