The two packages seem to be based largely on the same github code ( https://github.com/Legrandin/pycryptodome ), with different pypi release packages (https://pypi.org/project/pycryptodome/ and https://pypi.org/project/pycryptodomex/ , respectively). dev-python/pycryptodomex::science seems to be the “better” one as it does not conflict with dev-python/pycrypto. From the github README: """ The installation procedure depends on the package you want the library to be in. PyCryptodome can be used as: * an almost drop-in replacement for the old PyCrypto library. You install it with: pip install pycryptodome In this case, all modules are installed under the Crypto package. One must avoid having both PyCrypto and PyCryptodome installed at the same time, as they will interfere with each other. This option is therefore recommended only when you are sure that the whole application is deployed in a virtualenv. * a library independent of the old PyCrypto. You install it with: pip install pycryptodomex In this case, all modules are installed under the Cryptodome package. PyCrypto and PyCryptodome can coexist. """ But perhaps they should both be provided. Unsure whether they should be handled as separate packages as per the pypi tarballs, or whether the switch should be done dynamically via a USE flag based on the common github source code.
No, use dev-python/pycryptodome and fix the imports in the packages using it. It's really easy. The *only* difference between them is the module name: https://github.com/p0dalirius/pydsinternals/commit/05904ec91b230150c04ba10bb4556450eead5438. pycryptodomex was in ::gentoo before and was last-rited.
Right, that's what the README says — on account of the different name it doesn't collide with dev-python/pycrypto. Why prevent the option of installing them both on one system? In a sense pycryptodomex seems to be a namespace fix. Interestingly ::gentoo doesn't seem to actually distribute dev-python/pycrypto, even though the dev-python/pycryptodome ebuild has `!dev-python/pycrypto` in `RDEPEND` — so the advantage is currently just theoretical though it needn't remain so.
For the same reason we don't include several copies of the same packages.
