Modulo waiting for mips to catch up, the transition to add python3.5 as a supported python3 version is done, with the following exceptions [1]:
apparmor: #799449 FTBFS: test suite segfaults on mips and mipsel
pygpgme: #797776 FTBFS: Ran 55 tests in 54.866s: FAILED (failures=2, errors=2)
woo: #800407 FTBFS with python3.5 due to test failures
pygccjit: #800789 FTBFS due to test failures during binNMU for python3.5
support
healpy: #754803 out-of-date binaries
#799694 FTBFS on ppc64(el): No module named _tkinter
#800672 FTBFS: Tests require X environment
pandas: #790024 package pandas FTBFS on big-endian
#790924 FTBFS: copy() got an unexpected keyword argument
'font'
#790925 FTBFS on armhf and sparc: Bus error in
test_append_frame_column_oriented
That's six packages still needing work out of 182, so not bad. I would
appreciate any help people can provide on fixing these. pygpgme is probably
the most concerning since it's not a leaf package.
Additionally, looking ahead to the next transition that makes python3.5 the
default python3, it would be good to look at the packages that build-dep on
python3-dev and see if it's reasonable to have them build-dep on python3-all-
dev and build for all supported python3 versions.
Packages that only build for the default version will break until rebuilt as
soon as the default changes, whereas extensions that are built for all
supported python3 versions continue to work just fine. The fewer default only
packages we have, the less breakage goes with changing the default [2]. I
have not investigated these at all.
Scott K
[1] https://release.debian.org/transitions/html/python3.5.html
[2]
https://bugs.debian.org/cgi-bin/bugreport.cgi?filename=python3-dev.list;bug=798999;msg=84;att=1
signature.asc
Description: This is a digitally signed message part.
