Addressed renames for six, pyyaml an pyflakes to use python34-* where needed. 
I'd like to wait for a separate branch to sort our python3* issues on CentOS to 
keep this branch a bit more focused as a "best-effort" for python34 there. Our 
existing ci can use this current branch for python2 CentOS package builds, so 
we can drop our current dependency/setup duplication. 

   As you suggested, there are likely a couple of bugs we'll need to sort when 
we attempt full py3 package support on CentOS. When we tackle python3 support 
in earnest on CentOS, we may also have to add the facility to blacklist/ignore 
certain optional runtime requirements which we find don't exist for python3 in 
CentOS (like pyserial, jsonschema etc.). 
-- 
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/325342
Your team cloud-init commiters is requested to review the proposed merge of 
~chad.smith/cloud-init:ci-deps into cloud-init:master.

_______________________________________________
Mailing list: https://launchpad.net/~cloud-init-dev
Post to     : cloud-init-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~cloud-init-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to