IN THIS ARTICLE
Describes how to update your Python SDK
REQUIREMENTS
- Qumulo cluster
DETAILS
With Python 2.7's end of life now more than a year behind us, Qumulo has made the decision to discontinue support for Python 2.7 in our Python SDK and qq command line utility. Qumulo Core 4.0.0 is the final release for which we published a new Python 2.7 SDK. Starting with Qumulo Core 5.1.0, the Python SDK will only support Python 3.8 (and higher).
What does this mean for you? The Qumulo Core 4.0.0 Python 2.7 SDK will continue to be compatible with the Qumulo Core REST API in releases up until Qumulo Core 4.1.0, which should ship some time in May 2021. However, any new REST APIs published after Qumulo Core 4.0.0 is released will be unavailable in the Qumulo Core 4.0.0 Python 2.7 SDK. Any REST APIs marked as deprecated in Qumulo Core 4.0.0 and later will cease to work in the Python 2.7 SDK after Qumulo Core 4.1.0.
Note also that, starting with Qumulo Core 4.0.1, the standalone qq command line utility available via the API & Tools page in the cluster Web UI will require Python 3.8 (or higher) to be installed in order to run.
Upgrading to the Python 3.8 SDK
To install the Python 3.8 version of the Qumulo Python SDK, you can simply run the following command:
pip3 install qumulo_api==x.x.x
Replace "x.x.x" is the version of the SDK you wish to install. Qumulo recommends keeping the version of the SDK that you're using in sync with the version of your cluster.
General Recommendations
We at Qumulo have undergone our own journey of converting our 4000+ file Python codebase from Python 2.7 to Python 3 and highly recommend the following tools:
- The future package, which aids in transitioning code from Python 2.7 to Python 3.
- mypy, which allows enforcement of static type checking in both Python 2.7 and Python 3 and is essential in ensuring that your refactoring is safe.
RESOLUTION
You should now be able to successfully upgrade your Python SDK
ADDITIONAL RESOURCES
Getting Started with the Qumulo Core REST API
Like what you see? Share this article with your network!
Comments
0 comments