On Tue, Jun 05, 2018 at 04:48:00PM -0400, Zane Bitter wrote:
> On 05/06/18 16:38, Doug Hellmann wrote:
> > Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400:
> > > We've talked a bit about migrating to Python 3, but (unless I missed it)
> > > not a lot about which version of Python 3
On 06/05/2018 02:55 PM, Zane Bitter wrote:
[snip]
The list of breaking changes in 3.6 is quite short (although not
zero), so I wouldn't expect too many roadblocks:
https://docs.python.org/3/whatsnew/3.6.html#porting-to-python-3-6
I think we can split the problem into two parts:
* How can we d
On 05/06/18 16:38, Doug Hellmann wrote:
Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400:
We've talked a bit about migrating to Python 3, but (unless I missed it)
not a lot about which version of Python 3. Currently all projects that
support Python 3 are gating against 3.5. Howev
Excerpts from Zane Bitter's message of 2018-06-05 15:55:49 -0400:
> We've talked a bit about migrating to Python 3, but (unless I missed it)
> not a lot about which version of Python 3. Currently all projects that
> support Python 3 are gating against 3.5. However, Ubuntu Artful and
> Fedora 26
On 2018-06-05 15:55:49 -0400 (-0400), Zane Bitter wrote:
[...]
> AIUI we're planning to switch the test nodes to Bionic, since it's
> the latest LTS release, so I'd assume that means that when we talk
> about running docs jobs, pep8 &c. with Python3 (under the
> python3-first project-wide goal) tha
We've talked a bit about migrating to Python 3, but (unless I missed it)
not a lot about which version of Python 3. Currently all projects that
support Python 3 are gating against 3.5. However, Ubuntu Artful and
Fedora 26 already ship Python 3.6 by default. (And Bionic and F28 have
been release
