Replace py312 with py313 for build with latest Python variant #154
Conversation
This file contains 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
This was referenced Dec 3, 2024
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.
When investigating #151, I noticed that there are now 3 Python variants being tested in the nightly builds: py39, py312, and py313. This is because tiledb-py-feedstock was recently migrated to py313 in conda-forge/tiledb-py-feedstock#246. Even though our nightly scripts request only py39 and py312, since the migration file exists, the rerendering keeps the py313 build.
Following the strategy I started in #132, this PR updates the nightly feedstock builds to only test with py39 and py313.
Here is a manual run of my internal branch that demonstrates that with this PR the py312 build is dropped.