This page contains link to the latest stable release of Libcloud. If you are interested in an older release, please visit the archive page.
Libcloud 3.8.0 (stable - Python 3.7+ only) - Released on August 10th, 2023
- apache-libcloud-3.8.0.tar.gz [asc] [sha256] [sha512]
- apache_libcloud-3.8.0-py2.py3-none-any.whl [asc] [sha256] [sha512]
Upgrade notes: Click
You are strongly encouraged to verify those packages using the Apache Libcloud developers KEYS. You can find information on how to do that in the “Quick package verification guide” section bellow.
Distribution specific packages
Libcloud is also available in standard repositories of many popular Linux distributions.
Ubuntu, Debian (apt)
Fedora, RedHat (yum)
Arch Linux (pacman)
FreeBSD (ports, packages)
OS X (MacPorts)
Anaconda (Linux, OS X, Windows)
Keep in mind that distribution packages may be out of date. If you want to make sure that you are using the latest version, you should install it by downloading the archive from this page or using pip.
The Python Package Index or PyPI is the official third-party software repository for the Python programming language.
We push all the releases to PyPi so you can also download and install the latest release using pip:
Keep in mind that
pip install command doesn’t verify the package signatures,
so if you are worried about that, you should manually download the package and
verify the signature using the steps described bellow.
Old releases can be found in the archive at https://www.apache.org/dist/libcloud/. We strongly recommend to not use those releases, but upgrade to the latest release available.
Source code can be found in our Git repository at http://gitbox.apache.org/repos/asf/libcloud.git
Read only mirror is also available on Github at https://github.com/apache/libcloud
Package verification guide
This section contains quick instructions on how to validate the release PGP signatures.
1.. Download the KEYS file from the Apache website
It is very important to only download
KEYS file from the Apache server which
is mentioned above.
2.. Import KEYS file
3.. Verify package with
.asc signature file
Example of a bad signature: