Dependencies: Explicitly use PyCaret >= 3 #35
Merged
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.
Problem
Looks like the package installer selects an old version of PyCaret when updating pandas, now after llvmlite has been bumped, which trips with a funny error message.
-- https://github.com/crate/academy-fundamentals-course/actions/runs/12187513828/job/33998467147?pr=27#step:6:107
Solution?
This patch bumps the requirements definition to explicitly use PyCaret >=3.
Q&A
@zanieb: Coming from #32 (comment), is it also related to this issue, that
uv
is acting so conservatively here that it is apparently biased to select the lowest available package version again?