Included requests_toolbelt in dependencies

topless · web-flow · commit db9404165b0b · 2018-02-03T14:03:28.000+01:00
I just tried to use the library in Gae and was missing the `requests_toolbelt`.
diff --git a/GAE.rst b/GAE.rst
@@ -13,7 +13,7 @@ Google App Engine uses virtual machines to do work and serve your application's
 Prerequisites
 *************
 
-Follow the `third party vendor library install instructions <https://cloud.google.com/appengine/docs/python/tools/using-libraries-python-27#vendoring>`_ to include the two dependency libraries listed in ``requirements.txt``: ``requests`` and ``requests_oauthlib``, as well as this ``python-twitter`` library. Typically you can just place the three module folders into the same place as your app.yaml file; it might look something like this:
+Follow the `third party vendor library install instructions <https://cloud.google.com/appengine/docs/python/tools/using-libraries-python-27#vendoring>`_ to include the dependency libraries listed in ``requirements.txt``: ``requests``, ``requests_oauthlib`` and ``requests_toolbelt``, as well as ``python-twitter`` library. Typically you can just place the  module folders into the same place as your app.yaml file; it might look something like this:
 
 | myapp/
 | &#9500;&#9472;&#9472; twitter/
@@ -52,4 +52,4 @@ If you plan to store tweets or other information returned by the API in Datastor
 
 Sockets
 ^^^^^^^^^
-When urllib3 is imported on App Engine it will throw a warning about sockets: ``AppEnginePlatformWarning: urllib3 is using URLFetch on Google App Engine sandbox...`` This is just a warning that you'd have to use the Sockets API if you intend to use the sockets feature of the library, which we don't use in python-twitter so it can be ignored.
+When urllib3 is imported on App Engine it will throw a warning about sockets: ``AppEnginePlatformWarning: urllib3 is using URLFetch on Google App Engine sandbox...`` This is just a warning that you'd have to use the Sockets API if you intend to use the sockets feature of the library, which we don't use in python-twitter so it can be ignored.
