python-sasl
Python wrapper for Cyrus SASL
how sasl3 is different from sasl package?
This is a fork from original work from Cloudera's package sasl package.
Original package wasn't maintained and had issue wth latest Python 3 releases, and also had runtime issues running
on RHEL6. Python sasl3 package solves these issues.
External dependencies
You need following external packages installed on the system to pip-install sasl3 :
- C compiler (e.g.
gcc) cyrus-sasl-develpackage for Cyrus header files.
Both can be installed with OS' package manager, e.g.
yum install gcc cyrus-sasl-devel.x86_64
to generate sasl/saslwrapper.cpp from the pyx file:
run ./recython.sh
1 maintainer
Metadata
1 maintainer
Release files for sasl3 0.2.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sasl3-0.2.11.tar.gz | 44.7 kB | Without provenance | Details |
Release files / sasl3-0.2.11.tar.gz
| Download URL | sasl3-0.2.11.tar.gz |
|---|---|
| Size | 44.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b821d73f89d034b08b67afa789c2bf3522127ba8591bf4d0f2c9900eb24dae3
|
|
BLAKE2b-256 checksum How to use checksums |
d89b147c3fe3908abb85f6ae961de1e135ed46fb9a483503563a8c06aa37abb1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/42.0.1.post20191125 requests-toolbelt/0.9.1 tqdm/4.39.0 CPython/3.6.9
|
Security for sasl3 0.2.11
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
