Python3.6 is already in Unstable and I expect to see it in Testing soon after Stretch is released.
I've just now uploaded a version of python3-defaults to Experimental that adds python3.6 as as supported (but not default) python3. If you have binary extensions packaged, please start testing with this version to make sure your package builds correctly with both python3.5 and python3.6 as supported. As a reminder (and for anyone new) we'll do the transition to python3.6 in three stages: - Add python3.6 as supported and rebuild all binary extensions to support both python3.5 and python3.6 - Switch to python3.6 as default - Drop python3.5 from supported and rebuild again to remove python3.5 support. Last time I compared my understanding of the Buster schedule with the python3.7 schedule, I recall concluding that we'd likely be on python3.6 for the Buster release (not sure that's still true). If so, we only have to do this once this cycle andI think the sooner the better. Scott K
