Skip to content

Conversation

@harryswift01
Copy link
Member

Summary

This PR will align the project’s CI configuration, documentation, and packaging metadata with the current Python support policy.

Changes

CI configuration updates:

  • Updated project-ci.yaml to use a matrix strategy across multiple operating systems.
  • Added testing for Python versions 3.12, 3.13, and 3.14.
  • Removed reliance on a single Python version in CI.

Documentation updates:

  • Updated getting_started.rst to reflect Python 3.12+ support.
  • Removed outdated references to unsupported Python versions.

Packaging metadata cleanup:

  • Removed the Python version classifier from pyproject.toml.
  • Prevented implying unsupported Python version compatibility.

Impact

  • Improves CI coverage across supported platforms and Python versions.
  • Ensures documentation accurately reflects supported Python versions.
  • Reduces confusion for users and contributors regarding Python compatibility.

@harryswift01 harryswift01 added this to the v1.1.0 milestone Feb 4, 2026
@harryswift01 harryswift01 requested a review from jimboid February 4, 2026 12:38
@harryswift01 harryswift01 self-assigned this Feb 4, 2026
@harryswift01 harryswift01 added documentation Improvements or additions to documentation CI Failure labels Feb 4, 2026
@harryswift01 harryswift01 linked an issue Feb 4, 2026 that may be closed by this pull request
@jimboid
Copy link
Member

jimboid commented Feb 4, 2026

Any insight into why the pre-commit started failing for Windows builds? As far as I can tell, you didn't change anything there..

@harryswift01
Copy link
Member Author

Any insight into why the pre-commit started failing for Windows builds? As far as I can tell, you didn't change anything there..

It wasn’t a change to pre-commit itself, the Windows CI runner runs commands in PowerShell by default, and the workflow was using Bash-specific syntax. That started failing on Windows even though Linux and macOS were fine. I’ve updated the step to explicitly run with Bash so it behaves the same on all platforms.

Copy link
Member

@jimboid jimboid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it is all working the way it should. Deprecating py3.11 is a good idea if things are starting to become incompatible.

@harryswift01 harryswift01 merged commit 75d3f96 into main Feb 4, 2026
27 checks passed
@harryswift01 harryswift01 deleted the 268-bug-sphinx-docs branch February 4, 2026 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Failure documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Sphinx Docs not currently compatible with Python v3.11

2 participants