| So, I won't repeat what Ed said - the tl;dr is that pyrax should support Python 2.6, and your point about dedicated servers only supporting CentOS6 is something we need to consider. As for the rest - yes. The communications and deprecation of python-cloudfiles was poorly handled. The crux of what happened is that python-cloudfiles was a part time project and ultimately superseded by the python-swiftclient work in OpenStack. We have requirements that for an SDK / tool to be officially supported, we have dedicated full time headcount to support and maintain the package(s) - the decision was made to proceed with Pyrax which leverages python-swiftclient and other openstack tools under the covers as the official Python SDK for Rackspace. This was not made clear to the users, or the community by any parties involved, and for that I apologize. We're continually working on better upstream communication/collaboration and this series of events (you're not the first to give us this feedback) has made us take a very hard look internally on how this is all managed and communicated. The good news is that Ed - our current Pyrax SDK maintainer is full time and dedicated to working with you and others on pyrax - this means the Python 2.6 support will be taken care of. Tangentially: Yes - python-novaclient and python-swiftclient from OpenStack will work on Rackspace Cloud - you can actually look at the Pyrax source to see that it uses these under the covers. Rackspace runs OpenStack with as few differences as possible so OpenStack tools should work great on Rackspace. So, in short: I apologize. The communications and management of this to upstream (the community) were poor, and we are renewing all of our efforts to focus on upstream first. Jesse |