Donald Stufft a56b0f6f5a Don't bundle certifi ... The idea behind requests supporting the use of certifi is so that an installation can get newer certificates simply by updating their copy of certifi instead of requiring a new version of requests. By bundling certifi we're essentially reverting this behavior, forcing people to update their copy of pip to get a new copy of certifi to update their certififcaates. Instead we'll use a globally installed certifi if it's available which will allow people to upgrade their certificates as requests intended.		2015-02-24 08:33:59 -05:00
..
packages	Upgrade the bundled requests to 2.5.0	2014-12-02 00:22:14 -05:00
__init__.py	Upgrade requests to 2.5.1	2015-01-28 13:19:24 -05:00
adapters.py	Upgrade the bundled requests to 2.5.0	2014-12-02 00:22:14 -05:00
api.py	Upgrade the bundled requests to 2.5.0	2014-12-02 00:22:14 -05:00
auth.py	Upgrade requests to 2.5.1	2015-01-28 13:19:24 -05:00
cacert.pem	Upgrade requests to 2.1.0	2013-12-05 19:41:49 -05:00
certs.py	Don't bundle certifi	2015-02-24 08:33:59 -05:00
compat.py	Upgrade requests to 2.5.1	2015-01-28 13:19:24 -05:00
cookies.py	Upgraded requests to 2.2.0	2014-01-09 16:49:19 -05:00
exceptions.py	Upgrade the bundled requests to 2.5.0	2014-12-02 00:22:14 -05:00
hooks.py	Rename pip.vendor.* to pip._vendor.* to ensure it's obviously private	2013-10-22 21:32:25 -04:00
models.py	Upgrade requests to 2.5.1	2015-01-28 13:19:24 -05:00
sessions.py	Upgrade the bundled requests to 2.5.0	2014-12-02 00:22:14 -05:00
status_codes.py	update requests to 2.4.1 and add certifi dependency	2014-09-10 12:22:24 -07:00
structures.py	update requests to 2.4.1 and add certifi dependency	2014-09-10 12:22:24 -07:00
utils.py	Upgrade requests to 2.5.1	2015-01-28 13:19:24 -05:00