nebula-orchestrator/worker

Migrate to Python 3.x

naorlivne opened this issue · 3 comments

Expected/Wanted Behavior

With Python 2.x nearing it's EOL Nebula should migrate to Python 3.x (with the current minor version target being the latest released version)

Actual Behavior

Nebula is is currently Python 2.7.x based

In order to ensure Python 3 compatibility the following will need to be taken to account:

  • Code refactoring to Python 3 - the following cheat sheet should provide a good starting point as to what might need changing - http://python-future.org/compatible_idioms.html
  • Ensuring all prereqs packages are compatible with Python 3 at the currently used version & updating\migrating out of them where not
  • Updating Shippable to use Python 3
  • Updating the Dockerfile to be based from Python-3.x

Also IMHO Python 2.x support following the switch should be optional but not a hard requirement, it's hard enough to support a complex system so should multi-version support like that prove too much work it can\should just be skipped.

completed the migration to python3.7 & pushed to master & 2.1.0