Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Branch: dev
Commits on Jun 21, 2012
  1. Adding jjmaestro to AUTHORS

    authored
  2. Adding akhenakh to AUTHORS

    authored
  3. Bumping version to 0.4.1

    authored
  4. POST with utf-8 not correctly handled

    authored
    Thanks to @akhenakh for the patch from #GH-32, which fixes #GH-31
Commits on May 24, 2012
  1. @jjmaestro
Commits on May 20, 2012
  1. Adding Imgur API tests

    authored
Commits on May 16, 2012
  1. Apparently requests now handles cookies properly

    authored
    So there is no need to set request.cookies to an emtpy dictionary, also a CookieJar object
    is expected to be passed.
Commits on May 10, 2012
  1. @funkatron
Commits on May 2, 2012
  1. @istruble

    Updating AUTHORS.

    istruble authored
    Two different people pointed out the sloppy fix I made
    to the TWITTER_CONSUMER_{KEY,SECRET} test values.
    Adding both Anisse Astier and Martin Trigaux to AUTHORS.
Commits on Apr 28, 2012
  1. @mart-e

    fix import error in tests.py

    mart-e authored
Commits on Apr 22, 2012
  1. Adding Ian Struble to AUTHORS

    authored
  2. Redoing test naming structure and removing advanced unittest methods

    authored
    This way this package can be tested with and old unittest package and old
    Python version.
  3. Merge branch 'dev' of git://github.com/istruble/requests-oauth into i…

    authored
    …struble
    
    Conflicts:
    	tests/tests.py
  4. Fixing Handling oauth_verifier and Token

    authored
    This fixes #GH-14 and #GH-16. Breaks backwards compatibility. Token is now
    a simpler object, there is no set_verifier method anymore. Instead passing
    `oauth_verifier` as data parameter is needed.
Commits on Mar 19, 2012
  1. @istruble
  2. @istruble

    Merge remote-tracking branch 'origin/dev' into dev

    istruble authored
    Conflict was basically just the WHAT_TO_TEST commit [1].
    Also using POST in test_twitter_oauth_request_token
    (reverting switch to GET in last commit [2]).
    
    [1]: 20a7a8a tests.py have now a WHAT_TO_TEST variable.
    [2]: da8a0f4 Broke tests out a little bit.
    
    Conflicts:
    	tests/tests.py
Commits on Mar 18, 2012
  1. If Content-Type is not application/x-www-form-urlencoded and not usin…

    authored
    …g header_auth
    
    We send data encoded in the url. This makes Twitter test `test_update_profile_image` pass,
    fixing issue #GH-17
Commits on Mar 17, 2012
  1. Returning None for non set values

    authored
    This should fix #GH-18
  2. tests.py have now a WHAT_TO_TEST variable.

    authored
    This allows to easily test one authentication system at a time if necessary
  3. Fixing _enc_params and cleaning data

    authored
    url used in requests is calculated different, if we reset _enc_params as we had to do before,
    we can lose GET parameters.
    
    Also if we are doing a POST request, if information gets encoded in the url, we clean data, for
    avoiding sending duplicate information, which makes many OAuth providers fail.
Commits on Mar 9, 2012
  1. @istruble

    Broke tests out a little bit.

    istruble authored
    Trying to identify which tests are valid and moving a very
    small amount of common code into setUp().
  2. @istruble
Commits on Mar 8, 2012
  1. @istruble

    Fixed typo in test_settings.

    istruble authored
    Changed repeated TWITTER config lines to CONSUMER from API.
Commits on Feb 29, 2012
  1. Sometimes Content-Type is not set

    authored
    Adding a test for a GET with params. In these cases data_and_params need
    to be set in order to work. See issue #GH-17
Commits on Feb 22, 2012
  1. Upgrading tests

    authored
    All tests against Twitter API are called with header_auth authentication and
    url query string authentication.
    
    Current version of requests-oauth only works with my fork of requests, due to
    this bug in requests:
    kennethreitz/requests#445
  2. Sometimes Content-Type is not set

    authored
    This is probably the final patch for issues #GH-10 and #GH-12
    
    The body of the request isn't included in the signature base string if the
    request's 'Content-Type' header isn't "application/x-www-form-urlencoded".
    
    Also, requests-oauth overwrites request.data, relying on requests reenconding
    correctly if `request.data` or `request.files` was modified in the hook. This
    way we avoid duplicating code from requests and hooks can alter body to be sent.
    
    This way we can also pull some parameters out of the data, such as oauth_callback.
    This way we get #GH-13 working.
Commits on Feb 21, 2012
  1. Using Content-Type following spec and adding oauth_signature

    authored
    This works on a better patch for #GH-12. It follows the spec definition and also
    includes the signature when posting when header_auth is not used.
Commits on Feb 12, 2012
  1. Data can be passed as a string to requests

    authored
    Adapting @gldnspud patch with @immunda's issue description.
Something went wrong with that request. Please try again.