<div dir="ltr">Thanks for the follow up, it's really helpful for us to support Python 3.6 smoothly in the future.</div><div class="gmail_extra"><br><div class="gmail_quote">2017-08-25 12:29 GMT+08:00 Ian Wienand <span dir="ltr"><<a href="mailto:iwienand@redhat.com" target="_blank">iwienand@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
In a recent discussion [1] I mentioned we could, in theory, use Fedora<br>
26 for Python 3.6 testing (3.6.2, to be exact).  After a few offline<br>
queries we have put theory into practice, sorted out remaining issues<br>
and things are working.<br>
<br>
For unit testing (tox), you can use the<br>
'gate-{name}-python36-{node}-<wbr>nv' job template with fedora-26 nodes.<br>
For an example, see [2] (which, I'm happy to report, found a real<br>
issue [3] :).  You may need to modify your bindep.txt files to install<br>
correct build pacakges for RPM platforms; in terms of general<br>
portability this is probably not a bad thing anyway.<br>
<br>
I have an up/down devstack test working with a minor change [4].  I<br>
will work on getting this more stable and more complete, but if this<br>
is of interest, reach out.  In general, I track the centos & fedora<br>
jobs fairly closely at [5] to try and keep up with any systemic<br>
issues.<br>
<br>
Although it is not exactly trivial, there is fairly complete<br>
instructions within [6] to help build a Fedora image that looks like<br>
the infra ones for testing purposes.  You can also reach out and we<br>
can do things like place failed nodes on hold if there are hard to<br>
debug issues.<br>
<br>
Thanks,<br>
<br>
-i<br>
<br>
[1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-August/120888.html" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/2017-<wbr>August/120888.html</a><br>
[2] <a href="https://git.openstack.org/cgit/openstack-infra/project-config/commit/?id=5fe3ba95616136709a319ae1cd3beda38a299a13" rel="noreferrer" target="_blank">https://git.openstack.org/<wbr>cgit/openstack-infra/project-<wbr>config/commit/?id=<wbr>5fe3ba95616136709a319ae1cd3bed<wbr>a38a299a13</a><br>
[3] <a href="https://review.openstack.org/496054" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>496054</a><br>
[4] <a href="https://review.openstack.org/496098" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>496098</a><br>
[5] <a href="http://people.redhat.com/~iwienand/devstack-status/" rel="noreferrer" target="_blank">http://people.redhat.com/~<wbr>iwienand/devstack-status/</a><br>
[6] <a href="https://git.openstack.org/cgit/openstack-infra/project-config/tree/tools/build-image.sh" rel="noreferrer" target="_blank">https://git.openstack.org/<wbr>cgit/openstack-infra/project-<wbr>config/tree/tools/build-image.<wbr>sh</a><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>ChangBo Guo(gcb)</div></div></div>
</div>