Skip to content
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

Merged
merged 1 commit into from
Apr 15, 2022

Conversation

grlee77
Copy link
Contributor

@grlee77 grlee77 commented Apr 14, 2022

Description

closes #6341

This PR imports imread, imsave directly from imageio.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

  • Docstrings for all functions
  • Gallery example in ./doc/examples (new features only)
  • Benchmark in ./benchmarks, if your changes aren't covered by an
    existing benchmark
  • Unit tests
  • Clean style in the spirit of PEP8
  • Descriptive commit messages (see below)

For reviewers

  • Check that the PR title is short, concise, and will make sense 1 year
    later.
  • Check that new functions are imported in corresponding __init__.py.
  • Check that new features, API changes, and deprecations are mentioned in
    doc/release/release_dev.rst.
  • There is a bot to help automate backporting a PR to an older branch. For
    example, to backport to v0.19.x after merging, add the following in a PR
    comment: @meeseeksdev backport to v0.19.x
  • To run benchmarks on a PR, add the run-benchmark label. To rerun, the label
    can be removed and then added again. The benchmark output can be checked in
    the "Actions" tab.

Try importing imread, imsave directly from imageio.v2 when available
@grlee77 grlee77 added 🔧 type: Maintenance Refactoring and maintenance of internals backport: 0.19.x labels Apr 14, 2022
@grlee77
Copy link
Contributor Author

grlee77 commented Apr 14, 2022

Looks like this is working as expected (The linux-cp3.9-pre job passed and that is the only one configured to fail on unexpected warnings).

Copy link
Member

@alexdesiqueira alexdesiqueira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks @grlee77!

@jni jni merged commit 5661d67 into scikit-image:main Apr 15, 2022
@grlee77
Copy link
Contributor Author

grlee77 commented Apr 15, 2022

@meeseeksdev backport to v0.19.x

meeseeksmachine pushed a commit to meeseeksmachine/scikit-image that referenced this pull request Apr 15, 2022
grlee77 added a commit that referenced this pull request Apr 15, 2022
…3-on-v0.19.x

Backport PR #6343 on branch v0.19.x (avoid warnings about change to v3 API from imageio)
pllim added a commit to pllim/jdaviz that referenced this pull request Apr 18, 2022
@pllim
Copy link

pllim commented Apr 18, 2022

Hello and thanks for this fix! May I know which release will have this?

@grlee77
Copy link
Contributor Author

grlee77 commented Apr 18, 2022

I can release a 0.19.3 release in the next week or so.

alexdesiqueira pushed a commit to alexdesiqueira/scikit-image that referenced this pull request May 24, 2022
pllim added a commit to pllim/jdaviz that referenced this pull request Jun 13, 2022
@lagru lagru added this to the 0.19.3 milestone Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔧 type: Maintenance Refactoring and maintenance of internals
Projects
None yet
Development

Successfully merging this pull request may close these issues.

imageIO warnings due to v2 -> v3 migration
5 participants