Abraham Elmahrek deeb9b6d60 HUE-2109 [core] Use MPL instead of LGPL for certificate bundle 11 yıl önce
..
docs f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
ext f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
requests f37ba45a98 [core] Add BeautifulSoup and have requests use it 11 yıl önce
.gitignore f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
.travis.yml f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
AUTHORS.rst f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
HISTORY.rst f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
LICENSE f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
MANIFEST.in f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
NOTICE deeb9b6d60 HUE-2109 [core] Use MPL instead of LGPL for certificate bundle 11 yıl önce
README.rst f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
requirements.txt f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
setup.py f37ba45a98 [core] Add BeautifulSoup and have requests use it 11 yıl önce
tasks.py f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce
test_requests.py f8aa93ac3c HUE-670 [core] Hue should use connection pool to talk to webhdfs 12 yıl önce

README.rst

Requests: HTTP for Humans
=========================

.. image:: https://badge.fury.io/py/requests.png
:target: http://badge.fury.io/py/requests

.. image:: https://travis-ci.org/kennethreitz/requests.png?branch=master
:target: https://travis-ci.org/kennethreitz/requests

.. image:: https://pypip.in/d/requests/badge.png
:target: https://crate.io/packages/requests/

Requests is an Apache2 Licensed HTTP library, written in Python, for human
beings.

Most existing Python modules for sending HTTP requests are extremely
verbose and cumbersome. Python's builtin urllib2 module provides most of
the HTTP capabilities you should need, but the api is thoroughly broken.
It requires an enormous amount of work (even method overrides) to
perform the simplest of tasks.

Things shouldn't be this way. Not in Python.

.. code-block:: pycon

>>> r = requests.get('https://api.github.com', auth=('user', 'pass'))
>>> r.status_code
204
>>> r.headers['content-type']
'application/json'
>>> r.text
...

See `the same code, without Requests `_.

Requests allow you to send HTTP/1.1 requests. You can add headers, form data,
multipart files, and parameters with simple Python dictionaries, and access the
response data in the same way. It's powered by httplib and `urllib3
`_, but it does all the hard work and crazy
hacks for you.


Features
--------

- 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
- Unicode Response Bodies
- Multipart File Uploads
- Connection Timeouts
- Thread-safety
- HTTP(S) proxy support


Installation
------------

To install Requests, simply:

.. code-block:: bash

$ pip install requests

Or, if you absolutely must:

.. code-block:: bash

$ easy_install requests

But, you really shouldn't do that.


Documentation
-------------

Documentation is available at http://docs.python-requests.org/.


Contribute
----------

#. 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`_ tag for issues that should be ideal for people who are not very familiar with the codebase yet.
#. If you feel uncomfortable or uncertain about an issue or your changes, feel free to email @sigmavirus24 and he will happily help you via email, Skype, remote pairing or whatever you are comfortable with.
#. Fork `the repository`_ on GitHub to start making your changes to the **master** branch (or branch off of it).
#. Write a test which shows that the bug was fixed or that the feature works as expected.
#. Send a pull request and bug the maintainer until it gets merged and published. :) Make sure to add yourself to AUTHORS_.

.. _`the repository`: http://github.com/kennethreitz/requests
.. _AUTHORS: https://github.com/kennethreitz/requests/blob/master/AUTHORS.rst
.. _Contributor Friendly: https://github.com/kennethreitz/requests/issues?direction=desc&labels=Contributor+Friendly&page=1&sort=updated&state=open