python 3.5 support

[Kevin Benton]

Bug to track support for python 3.5.

From PTG etherpad (https://etherpad.openstack.org/p/neutron-ptg-pike-final):

Support Python 3.5 - https://etherpad.openstack.org/p/ptg-pike-python35 - https://governance.openstack.org/tc/goals/pike/python35.html

The goal suggests all unit/functional/integration jobs to pass on py35 and gate on it.

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

[Ihar Hrachyshka (ihar-hrachyshka)]

We are going to use this etherpad to track neutron bits: https://etherpad.openstack.org/p/py3-neutron-pike

[Dan Radez (dradez)]

We test with 3.6 and 3.8 now. This bug is no longer valid.