Future 0.17: drop Python 2 support
Since the landing of omnibus-heptapod!3 (merged), the octobus/heptapod:testing-py2
Docker image is actually running Python 3 code, even though it has all the Python 2 versions available.
This is due to a mix of explicit configuration done by Omnibus (Rails application and Heptapod Shell) and PATH precedence (for the hgserve
service).
Of course we could fix it in various ways, but I'd prefer not even have to worry about it and the accompanying uncertainty.
We are also close to the point where Omnibus Heptapod can build a fully working image, hence the only added value of the heptapod-docker project is to provide a Python 2 version (see omnibus-heptapod!7 (merged) and omnibus-heptapod!5 (merged)).
We've had dual support since %Heptapod 0.13.0, about 4 months ago, and only had very minor glitches reported to us about it. Maybe it's simply time to just drop Python 2 support in Heptapod 0.17?
Task list:
-
push Python 3 only octobus/heptapod:testing
image -
remove testing-py3
andtesting-py2
tags -
update INSTALL_HEPTAPOD -
upon Heptapod 0.17.0rc1 release, remove the latest-py3
andlatest-py2
tags of the Docker image