Libcloud 3.5.1 released
We are happy to announce Libcloud v3.5.1.
This release includes a small bug / fix improvement which allows HTTP retrying code to also retry failed “raw” requests. In addition to that, it also includes improvement in the GCE compute driver to retrieve some resources lazily on demand instead of inside the driver constructor.
A list of all the changes can be found at https://libcloud.readthedocs.io/en/latest/changelog.html#changes-in-apache-libcloud-3.5.1.
Note on Python 3.5 support
Libcloud v3.5.0 dropped support for Python 3.5.
Python 3.5 has been EOL and non-supported for more than a year (https://endoflife.date/python) now and a lot of libraries (including some we depend on) have already dropped support for it.
Last release which still supports Python 3.5 is Libcloud v3.4.1.
Note on code style change (developers only)
To make formating and styling in our code base more consistent, we have re-formatted all the code with black (https://github.com/psf/black) and we will automatically enforce black code style (https://black.readthedocs.io/en/stable/) for all the new code going forward.
This should make it easier to contribute and read the code since all the code will be using the same style.
The release can can be downloaded from https://libcloud.apache.org/downloads.html or installed using pip:
pip install "apache-libcloud==3.5.1"
If you have installed Libcloud using pip you can also use it to upgrade it:
pip install --upgrade "apache-libcloud==3.5.1"
A page which describes backward incompatible or semi-incompatible changes and how to preserve the old behavior when this is possible can be found at https://libcloud.readthedocs.org/en/latest/upgrade_notes.html
Regular and API documentation is available at https://libcloud.readthedocs.org/en/v3.5.1/
Bugs / Issues
If you find any bug or issue, please report it on our issue tracker https://github.com/apache/libcloud/issues.
Don’t forget to attach an example and / or test which reproduces your problem.
Thanks to everyone who contributed and made this release possible! Full list of people who contributed to this release can be found in the CHANGES file.