v2.1

What's Changed

• Update client to respect the newer RateLimit header by @AlecRosenbaum in #115

Full Changelog: v2.0...v2.1

v2.0

Changes in this release:

• update 429 handling to use response headers rather than the json body
• (Breaking Change) Drop python 2 support
• Other minor or project-internal changes (update pytest, test on more recent python 3 versions, etc)

v1.4

This release fixes how the client handles 204 API responses (#108).

v1.3

This PR adds retries functionality for 502, 503, and 504 status codes

v1.1

This release changes the base URL for the Close API from https://app.close.io/api/v1/ to https://api.close.com/api/v1/

v1.0

We're happy to publish a stable v1.0 of our Close.io API wrapper! The main highlights of this release are:

• Significantly improved code quality, clarity, and documentation.
• Automatic retrying of rate-limited requests.
• Breaking change: Removal of the asynchronous code. If you relied on our async=True flag in the past, you'll have to refactor your application. You can choose to run multiple concurrent api.get/post/put/delete requests via threading, multiprocessing, concurrent.futures, gevent, etc., depending on your specific use case and environment.

v0.5

• Fixed adding a trailing slash for GET requests.
• Several fixes to the lead merge script.
• Dropped flawed Python v3.x support.
• Added script deleting tasks for inactive users.

v0.4

remove six from setup, bump version