HTTP for lazy, impatient, hubristic humans.
Project description
Clients provide requests wrappers which encourage best practices, particularly always using Sessions to connect to the same host or api endpoint.
Usage
Requests
Typical requests usage is redundant and inefficient, by not taking advantage of connection pooling.
r = requests.get('https://api.github.com/user', headers={'authorization': token})
r = requests.get('https://api.github.com/user/repos', headers={'authorization': token})
Sessions
Using sessions is the better approach, but more verbose and in practice requires manual url joining.
s = requests.Session()
s.headers['authorization'] = token
r = s.get('https://api.github.com/user')
r = s.get('https://api.github.com/user/repos')
Clients
Clients make using sessions easier, with implicit url joining.
client = clients.Client('https://api.github.com/', headers={'authorization': token})
r = client.get('user')
r = client.get('user/repos')
Resources
Resources extend Clients to implicitly handle response content, with proper checking of status_code and content-type.
resource = clients.Resource('https://api.github.com/', headers={'authorization': token})
for repo in resource.get('user/repos'):
...
Being session based, Clients also work seamlessly with other requests adapters, such as CacheControl.
See documentation for more examples.
Installation
$ pip install clients
Dependencies
Requests 2.4.2+
Python 2.7, 3.3+
Tests
100% branch coverage.
$ py.test [--cov]
Changes
0.2
Resource attribute upcasts back to a client
iter and download implement GET requests with streamed content
create implements POST request and returns Location header
update implements PATCH request with json params
__call__ implements GET request with params
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.