Port to cryptography.

[tomprince]

No description provided.

[rossengeorgiev]

Thanks, but in v1.0.0 I specifically moved away from cryptography, because it made installation more error prone. See b31354f, and even you go further back you can find the move to cryptography before that #17

[rossengeorgiev]

Potentially, both could be supported with cryptography being preferred (should have better performance) if available. Also, have it as an extra in setup.py

[tomprince]

I'm curious what kind of errors you are getting installing cryptography? I know the maintainers of it, and I know they spend a bunch of effort to ensure that there are wheels for all major platforms, so that installation shouldn't be an issue. I think the only semi-common platform they don't provide wheels for is alpine linux (and I suspect that is largely because there isn't a good standard of how to build compatible wheels; see pypa/manylinux#37 for example).

[rossengeorgiev]

It was long time ago, and I can't recall specifics. But it made installs slow and error prone due compilation step or having to install various libraries. Cygwin was painful, and I recall issues with linux and windows installs. The switch to pycryptodome was solely to get rid of these issues.

I've thought before about simply having both, and preferring cryptography if its available. Best of both worlds.

[tomprince]

due compilation step or having to install various libraries

That should no longer be necessary; cryptography added manylinux wheels in v2.0 (2017), which will be used by any recent version of pip (>8.1; 2016). (Although there aren't cygwin wheels).