-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New release on PyPI #839
Comments
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. |
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 three differences for me:
That being said, pysodium seems like a very simple and direct implementation of the libsodium apis. HTH! |
Thanks @gonatienza ! |
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.The text was updated successfully, but these errors were encountered: