[ckuehl]

Chris Lamb, the current Debian Project Leader, has said that it will not be in stretch but could potentially be available in stretch-backports:

> If someone puts in the work, sure :) There isn't a "they" in Debian... it's, well, volunteers doing the actual grunt work if they feel it's needed..

Source: https://www.reddit.com/r/debian/comments/5a0gcf/will_python_...

With that said, I've personally packaged a simple backport of Python 3.6 (currently 3.6.2) for Debian stretch. There are pre-built Debian packages available in the releases tab, and a one-liner in the README for how to build them yourself: https://github.com/chriskuehl/python3.6-debian-stretch

You can install these alongside the regular python3.5 installation (it doesn't replace it).

[scrollaway]

I actually came across your repo a few days ago!

I haven't tried it yet. I remember seeing that comment from Chris Lamb but I'm left wondering what the blockers are to getting 3.6 in backports. I messed around with another python3.6 deb (don't remember from where) and there were too many issues with it; namely with venvs.

[ckuehl]

I've been using my packaged version pretty extensively (mostly in virtualenvs) and haven't encountered any issues yet myself, but would definitely be interested to hear (either on GitHub or here) what issues you encountered and if they occur with my packaged version as well.

I wouldn't really expect any issues since it doesn't replace `/usr/bin/python3` (it just adds a `/usr/bin/python3.6`), but it's definitely possible I just haven't run into them.

[scrollaway]

IIRC, the python3.6 from testing was causing inconsistencies in the /lib packages shipped inside the virtualenv (like inconsistent versions would get imported). I'll definitely give your package a shot!