Requests: The Simple (e.g. usable) HTTP Module
Most existing Python modules for dealing HTTP requests are insane. I have to look up everything that I want to do. Most of my worst Python experiences are a result of the various built-in HTTP libraries (yes, even worse than Logging).
But this one’s different. This one’s going to be awesome. And simple.
Really simple.
Features
- Extremely simple GET, HEAD, POST, PUT, DELETE Requests
Simple HTTP Header Request Attachment
Simple Data/Params Request Attachment
- Simple Basic HTTP Authentication
Simple URL + HTTP Auth Registry
Usage
It couldn’t be simpler.
>>> import requests
>>> r = requests.get('http://google.com')
HTTPS? Basic Authentication?
>>> r = requests.get('https://convore.com/api/account/verify.json')
>>> r.status_code
401
Uh oh, we’re not authorized! Let’s add authentication.
>>> conv_auth = requests.AuthObject('requeststest', 'requeststest')
>>> r = requests.get('https://convore.com/api/account/verify.json', auth=conv_auth)
>>> r.status_code
200
>>> r.headers['content-type']
'application/json'
>>> r.content
'{"username": "requeststest", "url": "/users/requeststest/", "id": "9408", "img": "censored-long-url"}'
API
Requests:
All request functions return a Response object (see below).
- GET Requests
>>> request.get(url, params={}, headers={} auth=None) <request object>- HEAD Requests
>>> request.head(url, params={}, headers={} auth=None) <request object>- PUT Requests
>>> request.put(url, data='', headers={}, auth=None) <request object>- POST Requests
>>> request.post(url, data={}, headers={}, auth=None) <request object>- DELETE Requests
>>> request.delete(url, params={}, headers={}, auth=None) <request object>
Responses:
- Request.status_code:
(Integer) Received HTTP Status Code Response
- Request.headers:
(Dictionary) Received HTTP Response Headers
- Request.content:
(Bytes) Received Content
HTTP Authentication Registry:
You can register AuthObjects to automatically enable HTTP Authentication on requests that contain a registered base URL string.
>>> requests.add_autoauth(url, authobject)
Installation
To install requests, simply:
$ pip install requests
Or, if you absolutely must:
$ easy_install requests
But, you really shouldn’t do that.
Contribute
If you’d like to contribute, simply fork the repository, commit your changes to the develop branch (or branch off of it), and send a pull request. Make sure you add yourself to AUTHORS.
Roadmap
Sphinx Documentation
Exhaustive Unittests
History
0.2.0 (2011-02-14)
Birth!
0.0.1 (2011-02-13)
Frustration
Conception
3 maintainers
Metadata
3 maintainers
Release files for requests 0.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 | |
|---|---|---|---|---|
| requests-0.2.0.tar.gz | 5.5 kB | Without provenance | Details |
Release files / requests-0.2.0.tar.gz
| Download URL | requests-0.2.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
813202ace4d9301a3c00740c700e012fb9f3f8c73ddcfe02ab558a8df6f175fd
|
|
BLAKE2b-256 checksum How to use checksums |
babbdfa0141a32d773c47e4dede1a617c59a23b74dd302e449cf85413fc96bc4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for requests 0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
