We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
VideoHash results in:
AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
Due to PIL.Image v10+ having deprecated ANTILIAS; fix appears to be LANCZOS or pinning PIL < 10:
https://pillow.readthedocs.io/en/stable/releasenotes/10.0.0.html#constants
To Reproduce
Install via pip with PIL and pillow from brew (currently 10.0.0)
pip
pillow
brew
VideoHash("path/to.mp4")
Expected behavior
Object with .hash and no AttributeError
.hash
Screenshots
N/A
Please complete the following information:
Additional context
I think this would be a good first issue for another contributor. Should I attempt a PR?
The text was updated successfully, but these errors were encountered:
This is fixed in PR #109 but it still needs to be merged.
Sorry, something went wrong.
Worked for me pip install Pillow==9.5.0
pip install Pillow==9.5.0
This causes security issues. There are known DoS attacks that exploit versions of Pillow older than 10.0.1
10.0.1
I've fixed the issue in my fork of this repository "videohash2": https://github.com/Demmenie/videohash2 https://pypi.org/project/videohash2/
No branches or pull requests
Describe the bug
VideoHash results in:
Due to PIL.Image v10+ having deprecated ANTILIAS; fix appears to be LANCZOS or pinning PIL < 10:
https://pillow.readthedocs.io/en/stable/releasenotes/10.0.0.html#constants
To Reproduce
Install via
pip
with PIL andpillow
frombrew
(currently 10.0.0)Expected behavior
Object with
.hash
and no AttributeErrorScreenshots
N/A
Please complete the following information:
Additional context
I think this would be a good first issue for another contributor. Should I attempt a PR?
The text was updated successfully, but these errors were encountered: