Skip to content

Conversation

@osmith42
Copy link
Collaborator

PyCryptodome modules are available in Crypto for legacy compatibility with the old PyCrypto library, and in Cryptodome. Switch to the non-legacy name, so the Debian 12 package python3-pycryptodome can be used (there is no python3-pycrypto package in Debian anymore).

See also:

PyCryptodome modules are available in Crypto for legacy compatibility
with the old PyCrypto library, and in Cryptodome. Switch to the
non-legacy name, so the Debian 12 package python3-pycryptodome can be
used (there is no python3-pycrypto package in Debian anymore).
@laf0rge
Copy link

laf0rge commented Oct 31, 2025

LGTM!

@Takuto88
Copy link
Collaborator

Takuto88 commented Nov 1, 2025

Looks innocent enough but: It could break installations without re-running pip install -r requirements.txt again if the dependency is not available in the venv / system python already. Still we should adopt it IMHO for future proofing.

@nickvsnetworking Since pyHss aims to follow a SemVer scheme: An in-place upgrade that might fail due to changed dependency APIs would be a breaking change IMHO. So this should land in a 2.0 release and be documented somewhere. Maybe in CHANGELOG.md?

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

Successfully merging this pull request may close these issues.

3 participants