python 3.5 support
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Bug to track support for python 3.5.
From PTG etherpad (https:/
Support Python 3.5 - https:/
The goal suggests all unit/functional
How do we keep the job list stable and manageable? Do we duplicate each job, or start deprovisioning some py27 jobs?
choose some jobs - tempest job, functional
for some reason, on my machine, the fullstack tests were running under Python 3.5 nice!
for tempest, we will need to pick a single existing full job (at least) and switch it to py3,
preferrably -nv so that it's safer to switch without lockstep changes in project-config
look into project-config for job definitions for stadium py35 jobs
We are going to use this etherpad to track neutron bits: https:/ /etherpad. openstack. org/p/py3- neutron- pike