Switch from pycryptodome to pycryptodomex #12
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pycryptodome is for / with backwards compatibility with the no longer mainainted pycrypto, the X is for the next version from the same developers.
As HiveMind-core does not need any pycrypto backwards compatibility using pycryptodome pycryptodomex is maybe prefered. It has no influence other then the installed location of the package. Hence it even uses the exact same pacjage files, yet pycryptodomex is the "new way to go" (No clue what the future will bring, I guess at some point pycryptodome is also no longer supported)