-
Notifications
You must be signed in to change notification settings - Fork 17
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
Why use pycryptodome < 3.4 ? #2
Comments
FWIW, this now fails
|
lol this is the only reason i need to fork this repo cough first fork cough, because i'm building an application, that because of GDPR, needs security, not failure |
i basically just need to fork it and substitute in the newer dependency |
There seems to be no movement on the issue for quite a while. Are there any restrictions that do not allow using newer versions? |
setup.py
specifiespycryptodome >=3.3.1, <3.4.0
. The latest version of pycryptodome is 3.4.11 (see the pycryptodome changelog).Is there a reason not to use 3.4.11?
The text was updated successfully, but these errors were encountered: