-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ecommerce Bridge API #43
Ecommerce Bridge API #43
Conversation
Upstream changes
…some Python 2 specific code
Ecommerce Bridge Endpunkte
Oops, thanks for catching that! Sorry that I unintentionally caused that bug with the style commit - I should've been more careful with that. I also need to get the new tests added into the Travis-CI config, as well as fixed up with a new API key! I'm also in the process of getting our own test API key that we can hopefully use for full on integration tests instead of using the |
This is now included in the latest release Thanks so much for your contributions! 😄 |
This PR adds a client for a few (probably the most important) of the Ecommerce Bridge API endpoints.
It also contains additions/changes to a few other things:
if
block was entered and would therefore result in an error in any other case. This was reverted in this PR while making the type of this variable consistent for each case.HTTP(S)Connection
objects. It offers some utilities to quickly check if certain requests would have been made if it was a real connection. It is used in the unit tests for the Ecommerce Bridge endpoints.__unicode__
anymore in Python 3) as well as some unnecessary conversion attempts like trying to decode a value that already is astr
.The PR contains tests for all added Ecommerce Bridge endpoints. They can be run using
tox -- hubspot3/test/test_ecommerce_bridge.py
with a local tox setup (hence the introduction of{posargs}
intox.ini
) or simplypy.test hubspot3/test/test_ecommerce_bridge.py
for a single Python version. The tests must be limited like this because the other tests are still problematic due to #40.(black was already applied in between certain commits, but it certainly wouldn't hurt to run it again after merging.)