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

Drop v2, apply v3 as the only imageio interface. #1011

Open
evan0greenup opened this issue Jun 21, 2023 · 0 comments
Open

Drop v2, apply v3 as the only imageio interface. #1011

evan0greenup opened this issue Jun 21, 2023 · 0 comments

Comments

@evan0greenup
Copy link

At this stage, I believe the API of imageio is stable enough.

Everytime when import image, import imageio.v3 as iio is too inconvenient. And accessing its member with different name is not natural. Because, since everyone get used to use it as iio, why does this project named imageio instead of iio.

Frankly speaking, as the functionality and usage of this library. I don't think it will have intensive usage in source code as numpy even for graphic intensive project.

So, I would recommend to move everything in v3 to imageio.__init__.py to it more readable and convenient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant