pynacl
pynacl copied to clipboard
pyca
New release on PyPI
Are there plans to release the current version of main anytime soon? The current release 1.5.0 on PyPI is from January 2022. I've run into an issue that seems fixed by the current commit, probably due to the updated bundled libsodium, so it would be helpful to have an updated version on PyPI as well.
We should probably run a release soon, yes. There aren't a lot of new features, but that's okay.
That'd be very helpful, thanks! Do you have an idea when that could be? I'm working on a package that needs the current pynacl master, but I'd like to avoid pointing the dependency spec to the git master.
~@reaperhulk seems like the latest version (1.5.0) has been released a few weeks ago, is it safe to close this issue?~
I completely misread the year of the last release 1.5.0 as 2025 (it was 2022 :/)
Please disregard my comment
Yeah no I sitll need to get to this, we should definitely leave it open 😄
@reaperhulk honest question, what's the difference between PyNaCL and pysodium? I've been using Pysodium lately, seems fairly well maintained.
@santiagobasulto , they are both listed under libsodium bindings.
The main differences for me:
- pynacl and cryptography are both from pyca, which is owned by a group of contributors and not an individual contributor.
- pysodium does not include the libsodium release for which the bindings were written. I.e, among other possible errors, if you pip install it but libsodium is not there you will get a "Unable to find libsodium" error.
- pynacl includes some high level wrappers and documentation that make high level implementations safe and not bound to common implementation errors (like a basic nonce reuse).
- pynacl uses cffi, pysodium uses ctypes. From a performance standpoint there will be a difference.
That being said, pysodium seems like a very simple and direct implementation of the libsodium apis.
HTH!
@reaperhulk ... i agree ... we need it :)
I've implemented a python file like interface to encrypt with PyNacl (and others). More details here : https://github.com/bibi21000/NaclFile.
I've done some benchmarks to compare with other cryptographics tools : https://github.com/bibi21000/CofferFile/blob/main/BENCHMARK.md
PyNacl is the fastest and produce the smallest files
Congrats and ty 👍
+1
Would love to see a new release to make the windows arm64 wheels available.
A new release would be great. Testing with 3.14 is currently blocked for us since https://github.com/pyca/pynacl/pull/848 isn't released yet. We're already at b2, only a few months until the release candidates. The earlier this is resolved here, the earlier the testing can continue in downstream projects.
@cdce8p can you break down what we can help with to make this happen? This one?
The fix is already part of main, so all that's needed here AFAICT at the moment would be to publish a new release to PyPI. https://github.com/pyca/pynacl/commit/d33028e43b814615a33e231925eaddb0f679fa2b
I’ll be doing one right after cffi 2.0 is released.
cffi 2.0 might still take a while yet, perhaps into October or however long it takes. Assuming pynacl releases are not too arduous, a humble suggestion would be: release 1.6.0 without free-threading support (but all the other accumulated fixes) ASAP, and then do 1.6.1 once cffi 2.0 is out.
I’ll be doing one right after cffi 2.0 is released.
CFFI 2.0 is out! 🚀
https://github.com/python-cffi/cffi/releases/tag/v2.0.0
Yep! @ngoldbaum and I have been talking on IRC. There’s one pypy issue we need to sort out, but I’m planning to look at this tomorrow and see if I can’t get a release done.
3.14 and 3.14t support are merged. If there are any tasks that need doing to enable a release, I'd be happy to help out.
1.6.0 is released, huge thanks to all who contributed, especially @ngoldbaum for his extensive work on free-threaded Python.