Repository navigation
Require Python 3.12, which named-arrays has needed since 2.11 - #34
Merged
Merged
Conversation
ctis claimed to support Python 3.10, but every release of its dependency optika requires Python 3.11, so installing ctis on 3.10 failed with "No matching distribution found for optika". CI already tests only 3.11 and 3.12. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N6zUsPoxW26srMeWormpe8
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #34 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 24 24
Lines 883 883
=========================================
Hits 883 883
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
…eeds On Python 3.11, pip can install nothing newer than named-arrays 2.10.0, so ctis there would never get later fixes, such as the median of an empty pixel (sun-data/named-arrays#255). CI now tests Python 3.12 and 3.13, and the documentation builds on 3.12, which it was doing on 3.11 with named-arrays 2.10.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N6zUsPoxW26srMeWormpe8
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pyproject.tomlsays ctis supports Python 3.10, which was never true. Every release of optika requires Python 3.11, so on 3.10pip install ctisfails withNo matching distribution found for optika~=2.1, which reads like a bug in ctis.Python 3.11 doesn't work well either: named-arrays has required Python 3.12 since 2.11.0, so on 3.11 pip can install nothing newer than named-arrays 2.10.0. ctis users on 3.11 would never get later fixes, such as sun-data/named-arrays#255 or #256. optika itself still supports 3.11, but ctis doesn't have to.
Changes
pyproject.toml:requires-pythongoes from>=3.10to>=3.12..readthedocs.yml: the docs build on Python 3.12 instead of 3.11, which also means they now render with the latest named-arrays instead of 2.10.0.Before merging: update the ruleset
The
mainruleset requires the three<os>, Python 3.11 testchecks by name. This PR no longer runs them, so it stays blocked until the ruleset swaps those three for<os>, Python 3.13 test. Once this is merged, other open PRs (#32, #33) will need to mergemainto pick up the 3.13 jobs.Testing
🤖 Generated with Claude Code
https://claude.ai/code/session_01N6zUsPoxW26srMeWormpe8