@edwardpark97 Thanks for the PR. Could you also bump the minor version?

@fatihkurtoglu @shaun-scale How do I go about pushing this change to PyPi? Is it automatically done or is there some manual step needed?

@fatihkurtoglu @shaun-scale How do I go about pushing this change to PyPi? Is it automatically done or is there some manual step needed?

Sorry missed that comment earlier. Process for pushing package to PyPi is explained here:
https://github.com/scaleapi/scaleapi-python-client/blob/master/docs/pypi_update_guide.md

In order to deploy and publish a new version:
Create a new Release on GitHub
Create and assign a new tag in the release page with the following template: vX.Y.Z Please make sure X.Y.Z is matching the version in the _version.py.
i.e. If the version in _version.py is 2.3.1 then the tag should be v2.3.1
Provide release notes by following the Release Notes Template and filling relevant sections to your changes.

Yup just did it! Not totally sure if it successfully triggered or not but I guess I'll find out soon enough

https://app.circleci.com/pipelines/github/scaleapi/scaleapi-python-client
pypi_publish workflow seems to be run successfully!

FYI: There seems to be an issue in conda deployment: conda-forge/scaleapi-feedstock#10
Found an existing issue on conda-forge and will follow up with them conda-forge/conda-forge.github.io#1604