No release in ages

[ddevault]

It's been two years since the last release, but there are important changes in master that should be released. Will we see another release soon?

[dlitz]

Which changes in master are important to you? Because, frankly, the master branch has a lot of bugs and the next release might end up being a new branch on top of 2.6.1 with some things cherry-picked (but not everything).

[ddevault]

After further research, we actually need the features of 2.7a1 to be stable. Namely, I'm looking for 90d6d3d. Right now we're working on applying this patch alone to the current stable release.

[dlitz]

Great, thanks for the feedback!

Apologies for the long delay. PyCrypto is rather ancient, maintaining it is more tricky than you might think, and I haven't had enough time to fix the mess due to personal issues. My release-management priority has been to avoid silently breaking existing applications rather than adding new features. I usually point people developing new applications to https://github.com/pyca/cryptography and https://github.com/pyca/pynacl, which are cleaner and better-maintained.

[ddevault]

Thanks, but neither of those support what we need. Actually, cryptography does, but we were put off by the big red "hazard zone" warnings on the relevant pages of documentation.

[merlijn-sebrechts]

Hi @dlitz

Can you please edit the README.md and the documentation to reflect that you don't advise people to use this module in new projects? A lot of stackoverflow questions and blogs still reference this module as the de-facto python crypto implementation. You making an official statement might help this problem.

Kind regards