4. Applied Futurize stage 2 across the entire repo.

[amakhaba]

This PR does the following (Apply Futurize stage 2):

• Applies Futurize stage 2 across the entire repository.
• Update document generation in the Jenkinsfile.
• Added Py3 support on setup.py.

Definition of Done Checklist

• [ ] Unit tested (coded, passed, included)?
• [x] Requested at least 2 reviewers?

JIRA: MT-738

[mmphego]

@amakhaba please update branch by merging master into it and fixing up the conflicts.

Please also change the target branch from user/amakhaba/MT-738/Auto-code-format to master as branch user/amakhaba/MT-738/Auto-code-format is already in master and doesn't exists anymore.

See: How to modify a pull request on GitHub to change target branch to merge into?

[ajoubertza]

I'm afraid this PR is a bit of mess now - it shows all the changes from earlier PRs as well, including the black autoformatting. Also a heap of conflicts. Any ideas?

[mmphego]

I'm afraid this PR is a bit of mess now - it shows all the changes from earlier PRs as well, including the black autoformatting. Also a heap of conflicts. Any ideas?

Seems like there are 2 options (IMHO):

1. Close PR, branch off master, cherry-pick or create new commits and then new PR.
2. Merge master into current branch, change target branch to master and fix conflicts

But @amakhaba and @tockards can decide.

[ajoubertza]

Option 3: Make a new branch from master and just copy the files from this branch to that one. Make that a new commit.

Loses the commit history, but clean result and much easier.

[amakhaba]

@ajoubertza and @mmphego option 3 sounds like a better one. Can i finish up with the merge conflicts that i am addressing now and then we can plot a way forward

[amakhaba]

@ajoubertza @lanceWilliams @tockards @mmphego I will be closing this PR as it has become to difficult to review please checkout : user/amakhaba/MT-738/Applied-futurize-stage-2 and review for further modifications. For Review please Look at PR - 110