Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Best python bindings for Digital Ocean API?

Posted on February 12, 2015

By jasonnerothin

I’m building a python plugin library that interfaces with DO’s API.

I’ve tried the looked at the following python bindings:

apache-libcloud python-digitalocean

and find that both have their drawbacks.

Thoughts?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

pythonic

August 5, 2015

We use DOsa for our infrastructure code. Very Pythonic.

Andrew SB

February 12, 2015

I personally use python-digitalocean and have contributed to it. I am also working on porting Apache libcloud’s DigitalOcean driver to API v2. So I have some experience with both of them.

Currently libcloud is employing version 1 of the API and has less than full API coverage. I don’t expect it to ever cover every endpoint. The main reason to use it is if you are working on a project that need to interact with multiple cloud providers. It attempts to abstract away the specifics of each API and provide a common way to work with them.

python-digitalocean on the other hand is focused on the DigitalOcean API. There are a few others, but I have found it to have the most complete API coverage. It is under active development, and the main author is very receptive to suggestions and contributions from others. It’s what I suggest to anyone looking for a Python wrapper. I’d be interested to hear what you find lacking.

jasonnerothin

February 15, 2015

I’m going to follow your suggestion then. Even though we are supporting multiple cloud providers, we’re plugin based, so can choose our bindings on a provider per provider basis. Sounds like the python-digitalocean bindings are more fully-featured.

Thanks.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.