path to python3

Registered by Olivier Mattelaer on 2018-03-01

How to move to python3?
python2.7 ends of life is 2020 [python2.6 ends of life was 2014]
so we need to start the move...

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Olivier Mattelaer
Direction:
Approved
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Olivier Mattelaer on 2020-11-15

Related branches

Sprints

Whiteboard

My proposal here is
- drop support for Python 2.6 in the next version and only keep support for python 2.7. This will help the transition to Python 3

Then we have to decide a strategy.
- only support for python3. This means releasing MG6aMC with the only difference between the two code is the version of python supported (we should target to only support from 3.5 or 3.6 actually) -> Not the way to go!
- or target a smooth transition with a support of both py2.7 and 3.x for a given period.
Here two package are adviced:
  - futurize:
  - modernize:
futurize seems to produce more python3 compatible code but it relies on some non default package. So we will use modernize for the moment.
https://python-modernize.readthedocs.io/en/latest/index.html

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.