Majic Projects
Majic Ansible Roles
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Majic Ansible Roles / Closed Task MAR-149 Switch to Python 3
Go to the next issue (open or closed)
Go to the next open issue
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Task
  • Category
    Not determined
  • Targetted for
    5.0.0
  • Status
    Closed
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    24 hours
  • Time spent
    12 hours
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Description

At the moment Majic Ansible Roles are being used and tested against Python 2.7 only. However, support for Python 2.7 has already been dropped by the upstream project on January 1st, 2020 (about a week ago).

In addition to this, the wsgi_website and common roles also provide support for running applications using Python 2.7.

In order to ensure long-time support for Majic Ansible Roles, it is necessary to switch over to using Python 3 throughout the roles. Support for Python 2.7 should be dropped along the way.

The following should be done:

  • Switch to using Python 3 as default interpreter when running Ansible (both controller and remote machines).
  • Update to latest testing framework versions (because they support only Python 3).
  • Switch to using Python 3 in the test site environment.
  • Make sure all role tests are passing.
  • Make sure testsite deploys without problems.
  • Update project information to denote it as being Python 3-compatible only.
  • Update role reference documentation.
  • Update usage instructions. Make sure to mention that Python 3 interpreter should be used for the Python virtual environment.
  • Update the release notes.
Todos (0 / 0)
Issue created