Developer Information

The goal behind type annotations is to make developer lives easier byintroducing optional static typing for Python programs.

This allows you to catch bugs and issues which are related to variable typesearlier and faster (aka when you run locally either manually orintegrated in your editor / IDE and also as part of you CI/CD buildpipeline).

An example of how to use type annotations correctly is shown below.

This is needed because of how Libcloud utilizes meta programming for the and related methods (there is no other way without writinga mypy plugin to achieve that).

Mailing Lists

All of the communication about Libcloud development happens on our mailinglists.

  • - Moderated and low volume mailing list whichis only used for distributing important project announcements and updates.(announce-archive)
  • - General mailing list for developers(dev-archive)
  • - Commits messages and other automaticallygenerated notifications go to this mailing list.Keep in mind that unlike the others, this mailing list is fairly noisy.(notifications-archive, )

Archive of old incubator mailing lists:

Issue Tracker

For information how to run the tests and how to generate the test coveragereport, please see the Testing page.

Continuous Integration

For continuous integration we use Travis-CI. You can find build reports on thefollowing links:

Travis-CI builder is also integrated with Github which means that if you open apull request there, Travis-CI will automatically build it.

Test coverage report is automatically generated after every push and can befound at https://codecov.io/github/apache/libcloud?branch=trunk.