Update requests to 2.18.4

requests now has some external dependencies

.gitignore

@@ -1,2 +1,14 @@
 *.pyc
-*.pyo
+*.pyo
+.DS_Store
+lib/MANIFEST.in
+lib/Makefile
+lib/_appveyor
+lib/appveyor.yml
+lib/docs
+lib/ext
+lib/pytest.ini
+lib/requirements.txt
+lib/setup.*
+lib/tests
+lib/tox.ini

LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright 2015 Kenneth Reitz
+Copyright 2017 Kenneth Reitz
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

README.md

@@ -3,4 +3,4 @@ script.module.requests
 
 Python requests library packed for KODI.
 
-See https://github.com/kennethreitz/requests
+See https://github.com/requests/requests

addon.xml

@@ -1,16 +1,20 @@
 <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 <addon id="script.module.requests"
        name="requests"
-       version="2.12.4"
-       provider-name="kennethreitz, beenje">
+       version="2.18.4"
+       provider-name="kennethreitz">
   <requires>
-    <import addon="xbmc.python" version="2.14.0"/>
+    <import addon="xbmc.python" version="2.25.0"/>
+    <import addon="script.module.urllib3" version="1.22"/>
+    <import addon="script.module.chardet" version="3.0.4"/>
+    <import addon="script.module.idna" version="2.6"/>
+    <import addon="script.module.certifi" version="2017.07.27.1"/>
   </requires>
   <extension point="xbmc.python.module"
              library="lib" />
   <extension point="xbmc.addon.metadata">
     <summary>Python HTTP for Humans</summary>
-    <description>Packed for KODI from https://github.com/kennethreitz/requests</description>
+    <description>Packed for KODI from https://github.com/requests/requests</description>
     <platform>all</platform>
     <language></language>
     <license>Apache2</license>

changelog.txt

@@ -1,38 +1,42 @@
+[B]Version 2.18.4[/B]
+
+- Synchronize with requests 2.18.4
+
 [B]Version 2.12.4[/B]
 
-- Synchonize with requests 2.12.4
+- Synchronize with requests 2.12.4
 
 [B]Version 2.9.1[/B]
 
-- Synchonize with requests 2.9.1
+- Synchronize with requests 2.9.1
 
 [B]Version 2.9.0[/B]
 
-- Synchonize with requests 2.9.0
+- Synchronize with requests 2.9.0
 
 [B]Version 2.8.1[/B]
 
-- Synchonize with requests 2.8.1
+- Synchronize with requests 2.8.1
 
 [B]Version 2.7.0[/B]
 
-- Synchonize with requests 2.7.0
+- Synchronize with requests 2.7.0
 
 [B]Version 2.6.0[/B]
 
-- Synchonize with requests 2.6.0
+- Synchronize with requests 2.6.0
 
 [B]Version 2.5.3[/B]
 
-- Synchonize with requests 2.5.3
+- Synchronize with requests 2.5.3
 
 [B]Version 2.4.3[/B]
 
-- Synchonize with requests 2.4.3
+- Synchronize with requests 2.4.3
 
 [B]Version 2.3.0[/B]
 
-- Synchonize with requests 2.3.0
+- Synchronize with requests 2.3.0
 
 [B]Version 1.1.0[/B]
 

lib/AUTHORS.rst

@@ -1,19 +1,13 @@
 Requests is written and maintained by Kenneth Reitz and
 various contributors:
 
-Keepers of the Three Crystals
-`````````````````````````````
+Keepers of the Four Crystals
+````````````````````````````
 
 - Kenneth Reitz <me@kennethreitz.org> `@kennethreitz <https://github.com/kennethreitz>`_, Keeper of the Master Crystal.
 - Cory Benfield <cory@lukasa.co.uk> `@lukasa <https://github.com/lukasa>`_
 - Ian Cordasco <graffatcolmingov@gmail.com> `@sigmavirus24 <https://github.com/sigmavirus24>`_
-
-
-
-Urllib3
-```````
-
-- Andrey Petrov <andrey.petrov@shazow.net>
+- Nate Prewitt <nate.prewitt@gmail.com> `@nateprewitt <https://github.com/nateprewitt>`_
 
 
 Patches and Suggestions
@@ -174,3 +168,13 @@ Patches and Suggestions
 - Philipp Konrad <gardiac2002@gmail.com> (`@gardiac2002 <https://github.com/gardiac2002>`_)
 - Hussain Tamboli <hussaintamboli18@gmail.com> (`@hussaintamboli <https://github.com/hussaintamboli>`_)
 - Casey Davidson (`@davidsoncasey <https://github.com/davidsoncasey>`_)
+- Andrii Soldatenko (`@a_soldatenko <https://github.com/andriisoldatenko>`_)
+- Moinuddin Quadri <moin18@gmail.com> (`@moin18 <https://github.com/moin18>`_)
+- Matt Kohl (`@mattkohl <https://github.com/mattkohl>`_)
+- Jonathan Vanasco (`@jvanasco <https://github.com/jvanasco>`_)
+- David Fontenot (`@davidfontenot <https://github.com/davidfontenot>`_)
+- Shmuel Amar (`@shmuelamar <https://github.com/shmuelamar>`_)
+- Gary Wu (`@garywu <https://github.com/garywu>`_)
+- Ryan Pineo (`@ryanpineo <https://github.com/ryanpineo>`_)
+- Ed Morley (`@edmorley <https://github.com/edmorley>`_)
+- Matt Liu <liumatt@gmail.com> (`@mlcrazy <https://github.com/mlcrazy>`_)

lib/CODE_OF_CONDUCT.md

@@ -0,0 +1,3 @@
+Be cordial or be on your way.
+
+https://www.kennethreitz.org/essays/be-cordial-or-be-on-your-way

lib/CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contribution Guidelines
+
+Before opening any issues or proposing any pull requests, please do the
+following:
+
+1. Read our [Contributor's Guide](http://docs.python-requests.org/en/latest/dev/contributing/).
+2. Understand our [development philosophy](http://docs.python-requests.org/en/latest/dev/philosophy/).
+
+To get the greatest chance of helpful responses, please also observe the
+following additional notes.
+
+## Questions
+
+The GitHub issue tracker is for *bug reports* and *feature requests*. Please do
+not use it to ask questions about how to use Requests. These questions should
+instead be directed to [Stack Overflow](https://stackoverflow.com/). Make sure
+that your question is tagged with the `python-requests` tag when asking it on
+Stack Overflow, to ensure that it is answered promptly and accurately.
+
+## Good Bug Reports
+
+Please be aware of the following things when filing bug reports:
+
+1. Avoid raising duplicate issues. *Please* use the GitHub issue search feature
+   to check whether your bug report or feature request has been mentioned in
+   the past. Duplicate bug reports and feature requests are a huge maintenance
+   burden on the limited resources of the project. If it is clear from your
+   report that you would have struggled to find the original, that's ok, but
+   if searching for a selection of words in your issue title would have found
+   the duplicate then the issue will likely be closed extremely abruptly.
+2. When filing bug reports about exceptions or tracebacks, please include the
+   *complete* traceback. Partial tracebacks, or just the exception text, are
+   not helpful. Issues that do not contain complete tracebacks may be closed
+   without warning.
+3. Make sure you provide a suitable amount of information to work with. This
+   means you should provide:
+
+   - Guidance on **how to reproduce the issue**. Ideally, this should be a
+     *small* code sample that can be run immediately by the maintainers.
+     Failing that, let us know what you're doing, how often it happens, what
+     environment you're using, etc. Be thorough: it prevents us needing to ask
+     further questions.
+   - Tell us **what you expected to happen**. When we run your example code,
+     what are we expecting to happen? What does "success" look like for your
+     code?
+   - Tell us **what actually happens**. It's not helpful for you to say "it
+     doesn't work" or "it fails". Tell us *how* it fails: do you get an
+     exception? A hang? A non-200 status code? How was the actual result
+     different from your expected result?
+   - Tell us **what version of Requests you're using**, and
+     **how you installed it**. Different versions of Requests behave
+     differently and have different bugs, and some distributors of Requests
+     ship patches on top of the code we supply.
+
+   If you do not provide all of these things, it will take us much longer to
+   fix your problem. If we ask you to clarify these and you never respond, we
+   will close your issue without fixing it.