Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • heptapod heptapod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 161
    • Issues 161
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • heptapodheptapod
  • Issues
  • #353

Closed
Open
Created Oct 03, 2020 by Georges Racinet@gracinet🦑Owner4 of 4 tasks completed4/4 tasks

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 and testing-py2 tags
  • update INSTALL_HEPTAPOD
  • upon Heptapod 0.17.0rc1 release, remove the latest-py3 and latest-py2 tags of the Docker image
Edited Nov 26, 2020 by Georges Racinet
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking