Description of problem: python-libnacl is used to gain direct access to the functions exposed by Daniel J. Bernstein’s nacl library via libsodium. It has been constructed to maintain extensive documentation on how to use nacl as well as being completely portable. Version-Release number of selected component (if applicable): 1.7.2
Created attachment 12894 [details] Working proposal spec for python-libnacl
Created attachment 12895 [details] libacl patch
New packages are only added in cauldron unless it's needed to fix a bug in an existing stable release package. Once in cauldron, it can be added as a backport for the sable release. Also, what's the difference between this package and the existing package ... urpmq -i python3-pynacl Name : python3-pynacl Version : 1.4.0 Release : 1.mga8 Group : Development/Python Size : 522030 Architecture: x86_64 Source RPM : python-pynacl-1.4.0-1.mga8.src.rpm URL : https://github.com/pyca/pynacl/ Summary : Python binding to the Networking and Cryptography (NaCl) library Description : PyNaCl is a Python binding to libsodium, which is a fork of the Networking and Cryptography library.
CC: (none) => davidwhodginsVersion: 8 => Cauldron
I could be wrong now so in that case I'm very sorry, but if I compare where they get the source from I see that python3-pynacl uses https://github.com/pyca/pynacl and python3-libnacl uses https://github.com/saltstack/libnacl so I would think there's a difference.
pynacl uses cffi to make the calls into libsodium and libnacl uses python ctypes. libnacl presents a more simplified API and a more direct connector into libsodium. I made libnacl because I had packaging issues with pynacl years ago. Thats the main difference, some people have opted to use libnacl, usually because the API is a little simpler. But libnacl is a little slower because it uses the ctypes interface to call functions.
(In reply to Kristoffer Grundström from comment #5) > pynacl uses cffi to make the calls into libsodium and libnacl uses python > ctypes. libnacl presents a more simplified API and a more direct connector > into libsodium. I made libnacl because I had packaging issues with pynacl > years ago. > > Thats the main difference, some people have opted to use libnacl, usually > because the API is a little simpler. But libnacl is a little slower because > it uses the ctypes interface to call functions. That's the explanation i got from the maker.
Thanks for explaining the difference. Assigning to all packagers to consider.
Assignee: bugsquad => pkg-bugs