Avoid using global state about cloudconvert-python HOT 2 OPEN

The current design has historic reasons and I agree that a global client is a bad design. However, changing this would be a breaking change which we do want to avoid at this point.

We might change this with next major version but there are no fixed plans yet.

The repo is actively maintained and we are not aware of any current bugs. It supports all available features of the CloudConvert API, including the latest additions (Signed URLs). The last update has been at the end of March of this year. So I do not see your point of a "lack of activity". Our Python SDK is much less used than our other SDKs; most customers do use the PHP or node.js SDK. This is why you might see more "activity" there.

from cloudconvert-python.

Thanks for the quick reply. Indeed, the lack of activity comment was mainly about the repo having open issues and not having had any commits for some months.

Regarding breaking changes, I think a major version bump would avoid any issues there; alternatively it'd most likely be possible to just export a new client class with a currently-unused name and leave the existing parts as they are.

from cloudconvert-python.