Async interface to Red Hat Product Pages, using Twisted
Access Red Hat Product Pages’s REST API asyncronously (non-blocking) using the Twisted framework.
Simple example: Fetching a release
from txproductpages import Connection
from twisted.internet import defer, reactor
@defer.inlineCallbacks
def example():
pp = Connection()
# fetch a release
try:
release = yield pp.release('ceph-3-0')
# release is a Munch (dict-like) object.
print(release.name)
except Exception as e:
print(e)
if __name__ == '__main__':
example().addCallback(lambda ign: reactor.stop())
reactor.run()
More Examples
See examples/ directory
Packages that use this package
Metadata
Release files for txproductpages 1.2.0
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 | |
|---|---|---|---|---|
| txproductpages-1.2.0.tar.gz | 5.8 kB | Without provenance | Details |
Release files / txproductpages-1.2.0.tar.gz
| Download URL | txproductpages-1.2.0.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e67ccfd154457ebcfaa54ca9cf84dfec5ce53106fb20fe2e306c4cc86acd856
|
|
BLAKE2b-256 checksum How to use checksums |
34a4514834888ddb6f3a495bad8ca02360c37f831ecebaa66ccd033f3fe7ce63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.2 pkginfo/1.4.2 requests/2.22.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.37.0 CPython/3.7.5
|
Security for txproductpages 1.2.0
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.