/!DON’T USE IT, but use upstream python-rados, except you really can’t /!
Python libraries for the Ceph librados library with use cython instead of ctypes
This a standalone library initially comes from this Ceph PR https://github.com/ceph/ceph/pull/7621
But can be built against older version of Ceph from 10.2.X (jewel) to latest.
(For older version use cradox< 2.0)
This is designed for application that want to use a recent python-rados API without upgrading the whole ceph cluster.
Rados C handles provided by this library can’t be used with the ceph rbd.py or librbdpy.
The API of this python lib will be keep in sync with the upstream Ceph rados.py API.
Free software: LGPL 2.1
Documentation: http://docs.ceph.com/docs/master/rados/api/python/
Installation
Pre-requires:
$ sudo apt-get install cython librados2 librados-dev
Then, at the command line:
$ pip install cradox
Or, if you have virtualenvwrapper installed:
$ mkvirtualenv cradox $ pip install cradox
Usage
import cradox as rados
Functionnal Tests
Ceph packages must be installed, the suite create a temporary Ceph cluster run the tests and destroy it.
tox
Release files for cradox 2.1.2
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 | |
|---|---|---|---|---|
| cradox-2.1.2.tar.gz | 44.6 kB | Without provenance | Details |
Release files / cradox-2.1.2.tar.gz
| Download URL | cradox-2.1.2.tar.gz |
|---|---|
| Size | 44.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccda89326c615883a71a383a86e97b2fdbfad709dcf8ef2b983f519934918d68
|
|
BLAKE2b-256 checksum How to use checksums |
30a8f4790a3f5af7c7616dda7bd5cddbe31d3cf7c35319b700ff49e14ffa8153
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.9.1 pkginfo/1.4.1 requests/2.18.1 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.14.0 CPython/2.7.13
|
Security for cradox 2.1.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
