docs(blog): convert case to cases in blog posts #10560
Merged
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
cpcloud
force-pushed
the
classification-post-case-to-cases
branch
from
2e92e20 to
078da9b
Compare
cpcloud
approved these changes
Feb 10, 2025
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.
Note
I wanted to prep this to easy swap when 10.0 is released and
ibis.case()is deprecated. We should keep the current usage ofibis.case()until 10.0 is ready.Description of changes
I noticed today that the classification metrics blog post still used
ibis.case()rather thanibis.cases(). This was intended so that if readers installed using PyPI or conda, thecaseexample would still be viable.This fixes the usage in the following posts: