-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avoid warnings about change to v3 API from imageio #6343
Conversation
Try importing imread, imsave directly from imageio.v2 when available
Looks like this is working as expected (The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @grlee77!
@meeseeksdev backport to v0.19.x |
…3-on-v0.19.x Backport PR #6343 on branch v0.19.x (avoid warnings about change to v3 API from imageio)
because scikit-image fixed it in scikit-image/scikit-image#6343
Hello and thanks for this fix! May I know which release will have this? |
I can release a 0.19.3 release in the next week or so. |
because scikit-image fixed it in scikit-image/scikit-image#6343
Description
closes #6341
This PR imports
imread
,imsave
directly fromimageio.v2
when available to avoid a warning that has been causing recent CI failures. This also ensures there will not be an unexpected change in behavior to existing code once imagio's default changes to the v3 API. We can migrate to that API version at a later time.Checklist
./doc/examples
(new features only)./benchmarks
, if your changes aren't covered by anexisting benchmark
For reviewers
later.
__init__.py
.doc/release/release_dev.rst
.example, to backport to v0.19.x after merging, add the following in a PR
comment:
@meeseeksdev backport to v0.19.x
run-benchmark
label. To rerun, the labelcan be removed and then added again. The benchmark output can be checked in
the "Actions" tab.