[openstack-dev] [requirements][ec2-api] How about using boto3 instead of boto in requirements

Tony Breeds tony at bakeyournoodle.com
Tue Jun 20 07:15:59 UTC 2017

On Mon, Jun 19, 2017 at 09:33:02PM +0800, jiaopengju wrote:
> Hi Dims,
> I got response from core member of ec2-api. What do you think about it?
> ----------------------------------
> Hi,
> I don't treat adding new library as a problem.
> - I see that you don't remove boto - so your change doesn't affect ec2-api code.

Part of the role of the requirements team is to ensure that we don't end
up with several libraries that have significant overlap in
functionality.  Clearly boto and boto3 fall squarely in that camp.

What the requirements team needs is some assurance that switching to
boto3 is something that the ec2-api team would be able to do.  Running
on boto which has been deprecated in favor of boto3 make sense from a
lot of levels.  We're far enough into the Queens cycle that I doubt it'd
happen this cycle :(

Yours Tony.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170620/d647c0d6/attachment.sig>

More information about the OpenStack-dev mailing list