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).
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.
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.
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!
The OS python is there to satisfy other OS dependencies, and only occasionally for you.
If you care about the Python version, you are much better off with an independent python install, I personally recommend conda - it lets you run different python versions for different uses, all shielded from OS upgrades (whether minor dist-upgrade or complete distribution change -- or $DIETY forbid joining a Redmond religion).
I have heard good things about Enthought Python, but don't have experience with it. And you can always build the latest yourself and build a .dpkg for your company.
And then ./python-build -v 3.6.1 /opt/python-3.6.1 and you're done.
You'll have to manage your paths manually for your shell/terminal though, this is basically what you'll need to do, though this is for perl but can be easily adapted: http://tinyurl.com/y8h7lbt2
(note: I am not a member of the project just interested in reading some feedback)
> One of the benefits of Fedora for Python developers is the ease of setting up Python development. The Fedora Python Classroom Lab makes it even easier for teachers and instructors to use Fedora in their classrooms or workshops. Ready to use operating system with important stuff pre-installed - either with GNOME or as a headless environment for Docker or Vagrant. Teach Python on Fedora, with Fedora, using the stuff you love: IPython, Jupyter Notebook, multiple Pythons, virtualenvs, tox, git and more
> The Fedora Python Classroom Lab comes in 3 variants. Either you can run it in graphical mode with GNOME, or you can virtualize it with Vagrant or run it in a Docker container. You choose what fits your teaching environment the best.
> Users and developers are available in the #fedora-python IRC channel on irc.freenode.org for real-time chat.
> Users and developers are also available on the mailing list at python-devel@lists.fedoraproject.org.
I know Red Hat is not the best but maybe this might be worth looking into?
Not having it is so annoying since Stretch is basically there for the next few years and 3.6 is a very important Python release.
I've even been considering switching all my company's servers back to Ubuntu just for that...