Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/kennethreitz/requests3
Requests 3.0, for Humans and Machines, alike. 🤖
https://github.com/kennethreitz/requests3
forhumans http http-client kennethreitz python-requests python3 requests requests-module
Last synced: 5 days ago
JSON representation
Requests 3.0, for Humans and Machines, alike. 🤖
- Host: GitHub
- URL: https://github.com/kennethreitz/requests3
- Owner: kennethreitz
- License: cc0-1.0
- Created: 2019-04-18T12:23:31.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2020-01-11T05:47:20.000Z (almost 5 years ago)
- Last Synced: 2024-11-29T01:54:46.317Z (15 days ago)
- Topics: forhumans, http, http-client, kennethreitz, python-requests, python3, requests, requests-module
- Language: Python
- Homepage: https://3.python-requests.org/
- Size: 9.51 MB
- Stars: 790
- Watchers: 33
- Forks: 39
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Changelog: HISTORY.md
- Contributing: CONTRIBUTING.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
- Authors: AUTHORS.rst
Awesome Lists containing this project
README
Requests III: HTTP for Humans and Machines, alike.
==================================================
[](https://pypi.org/project/requests/)
[](https://pypi.org/project/requests/)
[](https://pypi.org/project/requests/)
[](https://github.com/requests/requests/graphs/contributors)
[](https://saythanks.io/to/kennethreitz)
**Requests III** is an HTTP library for Python, built for Humans and Machines, alike. **This repository is a work in progress, and the expected release timeline is "before PyCon 2020"**.
Behold, the power of Requests III:
```pycon
>>> from requests import HTTPSession
# Make a connection pool.
>>> http = HTTPSession()
# Make a request.
>>> r = http.request('get', 'https://httpbin.org/ip')
# View response data.
>>> r.json()
{'ip': '172.69.48.124'}
```
[](http://docs.python-requests.org/)
Requests III allows you to send *organic, grass-fed* **HTTP/1.1** & **HTTP/2** (wip) requests,
without the need for manual thought-labor. There's no need to add query
strings to your URLs, or to form-encode your POST data. Keep-alive and
HTTP connection pooling are 100% automatic, as well.
Besides, all the cool kids are doing it. Requests is one of the most
downloaded Python packages of all time, pulling in over ~1.6 million
installations *per day*!
Feature Support
---------------
Requests III is ready for today's web.
- Support for H11 & H2 protocols.
- Type-annotations for all public-facing APIs.
- Better defaults; required timeouts.
- ``async``/``await`` keyword & ``asyncio`` support.
- Compability with Python 3.6+.
While retaining all the features of [Requests Classic](https://2.python-requests.org/):
- International Domains and URLs
- Keep-Alive & Connection Pooling
- Sessions with Cookie Persistence
- Browser-style SSL Verification
- Basic/Digest Authentication
- Elegant Key/Value Cookies
- Automatic Decompression
- Automatic Content Decoding
- Unicode Response Bodies
- Multipart File Uploads
- HTTP(S) Proxy Support
- Connection Timeouts
- Streaming Downloads
- `.netrc` Support
- Chunked Requests
Satisfaction guaranteed.
Documentation
-------------
Fantastic documentation is available at
, for a limited time only.
How to Contribute
-----------------
1. Become more familiar with the project by reading our [Contributor's Guide](http://docs.python-requests.org/en/latest/dev/contributing/) and our [development philosophy](http://docs.python-requests.org/en/latest/dev/philosophy/).
2. Check for open issues or open a fresh issue to start a discussion
around a feature idea or a bug. There is a [Contributor
Friendly](https://github.com/requests/requests/issues?direction=desc&labels=Contributor+Friendly&page=1&sort=updated&state=open)
tag for issues that should be ideal for people who are not very
familiar with the codebase yet.
3. Fork [the repository](https://github.com/requests/requests) on
GitHub to start making your changes to the **master** branch (or
branch off of it).
4. Write a test which shows that the bug was fixed or that the feature
works as expected.
5. Send a [pull request](https://help.github.com/en/articles/creating-a-pull-request-from-a-fork) and bug the maintainer until it gets merged and
published. :) Make sure to add yourself to
[AUTHORS](https://github.com/requests/requests/blob/master/AUTHORS.rst).