Depreciation warnings for starters, and it'd not be hard to port existing code to a new libcloud version with proper upgrade guidelines.
It's probably as simple as %s/import\ libcloud/import\ libcloud.compute/ On Wed, Jan 12, 2011 at 7:06 AM, Tomaz Muraus <[email protected]> wrote: > Yeah, trying to still keep the old imports to work and just throwing a > DeprecationWarning in the next few versions sounds ok. > > On Tue, Jan 11, 2011 at 7:54 PM, Paul Querna <[email protected]> wrote: > >> One question not posed is the module name. >> >> ie, should it all be inside libcloud.storage? >> >> This would imply moving all our existing code to libcloud.compute, >> which is kinda a pain for upgrades, but I'm kinda a fan of maybe doing >> it for 0.5, but having the old imports work too for a few versions. >> >> Thoughts? >> >> Thanks, >> >> Paul >> >> >> On Tue, Jan 11, 2011 at 7:30 AM, Tomaz Muraus <[email protected]> wrote: >> > Hello all, >> > >> > I have posted a short proposal / ideas for the object storage API on the >> > libcloud wiki - http://wiki.apache.org/incubator/LibcloudStorageAPI >> > >> > Please post your feedback, opinions and ideas how to improve it. >> > >> > I think the next step after deciding how the API should look like (at >> least >> > approximately) should be >> > implementing the base API and creating a reference driver and then we can >> > move on from there :-) >> > >> > - Tomaz >> > >> > -- sengork
