make sure custom_data elem in dict works
fix requests version in setup.py
Merge pull request #91 from denibertovic/custom_data

make sure custom_data elem in dict works
Merge pull request #92 from denibertovic/request_version_fix

fix requests version in setup.py
fix search query encoding

this works with the new backend changes
small pep8 fixes
Fixes #74: fix data expansion bug
Merge pull request #94 from denibertovic/fix_expansion

Fix expansions
Merge pull request #93 from denibertovic/fix_wrong_encoding

fix search query encoding
fix id site test for python3
Merge pull request #96 from denibertovic/live_tests

some live tests fixes
add Github and Linkedin providers
forgot to remove httpretty from setup.py
bump requests to the newest version

This is required because the older requests version we used
have a buggy urllib3 vendored in that breaks the py3
integration (live tests were failing).

More info can be found here:
https://github.com/stormpath/stormpath-sdk-python/issues/69

It's worth noting that we could not use older versions than 2.3.0 because of
another bug that was fixed in that release.

https://github.com/kennethreitz/requests/issues/1887

This was only when using pyopenssl, which is optional, the bug
was not triggered if request falls back to the stdlibs ssl
implementation. Still, it would have failed loudly is users
were using pyopenssl for any reason.

I've bumped to the latest version cause I see no benefit in using the
older versions seeing as 2.3.0 (which is the lowest version we can use)
already introduces breaking API changes and the subsequent releases have
a lot of important bugfixes (and no API changes, accoring to the
changelog). Still this change may break users code if they interact with
requests directly.
Fix Shauthc1 auth scheme to work with requests

We handled bytestring in headers manually because of a bug
in the earlier versions of requests. Now that we use the newest version this
is no longer needed, and in fact doesn't work so we're removing it.
Merge pull request #97 from denibertovic/requests

New social providers and requests bug fix
make password reset flows consistent

reset_account_password now takes a token as a string representation.
This makes sense because the string is going to be extracted from the
URL anyway, the method handles the object creation and password reset
as usual. This change is to be consistent with
verify_password_reset_token which also takes a string.