Upgrade to Python 3.7.x

[jdemeyer]

Tarball: https://www.python.org/ftp/python/3.7.3/Python-3.7.3.tar.xz

CC: @fchapoton @embray @kiwifb @mkoeppe @slel

Component: packages: standard

Keywords: upgrade

Author: Jeroen Demeyer

Branch: 5a09cf1

Reviewer: Vincent Klein, Erik Bray, Frédéric Chapoton

Issue created by migration from https://trac.sagemath.org/ticket/25680

[jdemeyer]

Branch: u/jdemeyer/upgrade_to_python_3_7_0

[jdemeyer]

New commits:

2c67605

Upgrade to Python 3.7.0

[jdemeyer]

Commit: 2c67605

[jdemeyer]

Author: Jeroen Demeyer

[embray]

comment:3

I don't think we should be in any hurry on this. All the last ~year's work of Python 3 porting has been targeting Python 3.6, and I think I'd rather stick with that before risking throwing everything out of whack again.

Between Python 3.6 and 3.7 I suspect the differences, if any, will be minor. But I'd rather try to stabilize on 3.6 first (to which we're quite close), then deal with those differences, rather than change Python versions again. Also I don't know that Python 3.7 has been ported to Cygwin yet (although it does contain a number of useful fixes for Cygwin, I do know).

That said, if you know any specific changes in Python 3.7 (other than the aforementioned Cygwin fixes) that would actively make our porting effort easier I'd consider it...

[fchapoton]

comment:5

Jeroen has said elsewhere that islice will accept Sage integers instead of just ints.

I am again becoming tired and frustated by the slow pace of progress towards py3. And by the large amount of difficult work that remains..

[embray]

comment:6

Ah, I remember making an issue about that, but I don't think I followed what the resolution was.

[sagetrac-git]

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

1bfcdc8

Upgrade to Python 3.7.0