Hey, I'd like to have python 3.7 for 6.4 (not as the default version of course) and somewhere during 6.4 cycle we could switch over to it for our python ports.
I took 3.6 and adapted it for the new version. Does the test suite work for you? In my case it seems it never ends with "running: test_asyncio (2 min 52 sec)" until I ^c. If people have the same, I'll add TEST_IS_INTERACTIVE=Yes Attached, the diff for our current files and the tgz for the 3.7 directory. Comments? OK? Cheers, Daniel
? 3.7
Index: Makefile
===================================================================
RCS file: /cvs/ports/lang/python/Makefile,v
retrieving revision 1.68
diff -u -p -r1.68 Makefile
--- Makefile 8 Jul 2017 08:28:00 -0000 1.68
+++ Makefile 8 Sep 2018 18:20:36 -0000
@@ -3,6 +3,7 @@
SUBDIR =
SUBDIR += 2.7
SUBDIR += 3.6
+SUBDIR += 3.7
.include <bsd.port.subdir.mk>
Index: Makefile.inc
===================================================================
RCS file: /cvs/ports/lang/python/Makefile.inc,v
retrieving revision 1.124
diff -u -p -r1.124 Makefile.inc
--- Makefile.inc 3 Nov 2017 13:13:05 -0000 1.124
+++ Makefile.inc 8 Sep 2018 18:20:36 -0000
@@ -126,7 +126,7 @@ FAKE_FLAGS += RANLIB=:
# and QtWebKit require W|X mappings.
USE_WXNEEDED = Yes
-.if ${VERSION} == "3.6"
+.if ${VERSION} == "3.6" || ${VERSION} == "3.7"
ALL_TARGET = all
.else
ALL_TARGET = all ./Lib/plat-openbsd6
Index: python.port.mk
===================================================================
RCS file: /cvs/ports/lang/python/python.port.mk,v
retrieving revision 1.99
diff -u -p -r1.99 python.port.mk
--- python.port.mk 24 Jul 2018 12:10:10 -0000 1.99
+++ python.port.mk 8 Sep 2018 18:20:36 -0000
@@ -24,7 +24,8 @@ MODPY_VERSION ?= ${MODPY_DEFAULT_VERSION
# verify if MODPY_VERSION forced is correct
.else
. if ${MODPY_VERSION} != "2.7" && \
- ${MODPY_VERSION} != "3.6"
+ ${MODPY_VERSION} != "3.6" && \
+ ${MODPY_VERSION} != "3.7"
ERRORS += "Fatal: unknown or unsupported MODPY_VERSION: ${MODPY_VERSION}"
. endif
.endif
3.7.tgz
Description: application/compressed-tar
