Umm, that bugreport was resolved by migrating from the crypto module to cryptography, which is already a dependency of the package. Also, pycryptodome is not in fact in the repos, though pycryptodomex is (do read up on the difference) and would require modifying all imports downstream, which would be quite silly.
Assuming that we actually wanted to replace the (nonexistent) use of pycrypto with pycryptodome, it would anyways make more sense to file this against pycrypto rather than pick on one of its consumers...

Although it looks like the dependency on python2-crypto could be dropped altogether since it is no longer used, so I'll still assign this.