Hi, everyone:
I have a blueprint of freezer to support s3 storage driver [1], so I need to 
add boto3 to the requirements [2].
Why use boto3 but not boto?
Boto3 [3] isthe next version of Boto, is now stable and recommended for general 
use. It can be used side-by-side with Boto in the same project, so it is easy 
to start using Boto3 in your existing projects as well as new projects. Going 
forward, API updates and all new feature work will be focused on Boto3.

Boto3 requires botocore, jmespath and s3transfer. botocore and jmespath are 
already used by boto, this is because boto is used by ec2-api (and 
heat-cfntools, rally and swift3). After adding Boto3 to requirements, we will 
have old and new libraries ATM.

My suggenstion
How about using boto3 instead of boto? This will require us to do some 
migration about boto to boto3.

Anyone has ideas or suggesstions? Thank you very much!


Pengju Jiao
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to