Hi,
Thanks! I will try to use botocore instead of boto3 to find out whether the
code running or not.
jiaopengju
mail: [email protected]
原始邮件
发件人:Andrey [email protected]
收件人:OpenStack Development Mailing List (not for usage
questions)[email protected]; [email protected];
Alexandre [email protected]
发送时间:2017年6月20日(周二) 18:25
主题:Re: [openstack-dev] [requirements][ec2-api] How about using boto3instead of
boto in requirements
Hi,
We (ec2-api team) now in the middle of some investigations that should lead us
to either to remove boto from the code or to change it to botocore as we
decided previously.
We'll done with it to the middle of July.
Regards,
Andrey Pavlov.
On Tue, Jun 20, 2017 at 10:15 AM, Tony Breeds [email protected] wrote:
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.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
