Aiobravado
About
Aiobravado is the asyncio version of the bravado library for use with the OpenAPI Specification (previously known as Swagger).
aiobravado requires Python 3.5+ and allows you to use asynchronous programming when interacting with OpenAPI-enabled services. Here’s the breakdown of bravado packages and their use case:
bravado - Library to dynamically interact with OpenAPI/Swagger-enabled services. Supports Python 2.7+.
fido - HTTP client to enable asynchronous network requests for bravado. Supports Python 2.7+. Depends on twisted. Spins up a separate thread to handle network requests.
bravado-asyncio - asyncio-powered asynchronous HTTP client for bravado. Requires Python 3.5+. It is the default HTTP client for aiobravado, but can be used with bravado as well.
aiobravado - asyncio-enabled library to dynamically interact with OpenAPI/Swagger-enabled services. Supports basically all of the features of bravado. Requires Python 3.5+. No additional threads are created.
Example Usage
from aiobravado.client import SwaggerClient
client = await SwaggerClient.from_url('http://petstore.swagger.io/v2/swagger.json')
pet = await client.pet.getPetById(petId=42).result(timeout=5)
Documentation
More documentation is available at http://aiobravado.readthedocs.org
Installation
# To install aiobravado
$ pip install aiobravado
# To install aiobravado with optional packages recommended by aiohttp
$ pip install aiobravado[aiohttp_extras]
Development
Code is documented using Sphinx.
virtualenv is recommended to keep dependencies and libraries isolated.
Setup
# Run tests
tox
# Install git pre-commit hooks
tox -e pre-commit install
Contributing
Fork it ( http://github.com/sjaensch/aiobravado/fork )
Create your feature branch (git checkout -b my-new-feature)
Add your modifications
Add short summary of your modifications on changelog.rst under Upcoming release. Add that entry at the top of the file if it’s not there yet.
Commit your changes (git commit -m "Add some feature")
Push to the branch (git push origin my-new-feature)
Create new Pull Request
License
Copyright (c) 2013, Digium, Inc. All rights reserved. Copyright (c) 2014-2015, Yelp, Inc. All rights reserved.
Aiobravado is licensed with a BSD 3-Clause License.
Metadata
Release files for aiobravado 0.9.3
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 | |
|---|---|---|---|---|
| aiobravado-0.9.3.tar.gz | 14.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiobravado-0.9.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.5 kB
Release files / aiobravado-0.9.3.tar.gz
| Download URL | aiobravado-0.9.3.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d03b4a8f9fc08e07da6cb341796f605891b6c111c226504185ec1ee71586428e
|
|
BLAKE2b-256 checksum How to use checksums |
579c36c2eeb68d525d2df91b5913321626650eb2a1ff3fad493f38421e3078b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / aiobravado-0.9.3-py3-none-any.whl
| Download URL | aiobravado-0.9.3-py3-none-any.whl |
|---|---|
| Size | 18.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf7b43bee0bc0c7756a3294fb2af5f7c9a8dd5e5c3252890739c84d1f0356d51
|
|
BLAKE2b-256 checksum How to use checksums |
e2922cba66c6e470e2a68347e5789e89f79ac4cdbf0fff2dab5c2ec809780090
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for aiobravado 0.9.3
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.