incubator-libcloud mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roman Bogorodskiy <>
Subject [libcloud] ideas on improving exceptions usage
Date Thu, 05 Aug 2010 17:44:37 GMT

Some time ago I brought an 'exceptions' topic on IRC, basically, I think
it would be nice to make exceptions more centralised and unified among

The general idea is to create some base exception, e.g.
LibCloudException and subclass all other exception from it.

From a user perspective it will allow to identify libcloud exceptions
quite easily.

My proposal is pretty simple:

 - just add LibCloudException to libcloud.types
 - make other exceptions in libcloud.type be a subclass of 
 - eventually convert all the drivers to this scheme

I though about moving all the exceptions to a separate module but
considering that we have only handful of them I don't see much sense in
it. Also, I'm not sure it makes sense to introduce driver specific
exceptions... even if we need this we probably could introduce a
'driver' property for LibCloudException which would show the driver an
exception came from.

I've crafted a simple patch illustrating an idea:

Comments are welcome,

Roman Bogorodskiy

View raw message