Make Python3.6+ compliant

[deadbits]

To get a wider user base and ensure we can support both Python2.7 and Python3.6+, we'll need to make some changes:

• Ensure all dependencies from requirements.txt are Py3.6+ compatible
• Ensure all exceptions are handled correctly
• Handle print as print(foo) versus print foo
• Use fstrings and new format method in places where it makes sense:
• ...
• ... ongoing as I find more requirements

new: info(f'{artifact} tags: {result}')

original: info('%s tags: %s' % (artifact, result))

new: 
build_version = 'v{}.{}-{}_{}'.format(__app_major, rev_count.strip(), rev_hash.strip(), __app_stage)
app_version = 'v{}.{}_{}'.format(__app_major, rev_count.strip(), __app_stage)

old:
build_version = 'v%s.%s-%s_%s' % (__app_major, rev_count.strip(), rev_hash.strip(), __app_stage)
app_version = 'v%s.%s_%s' % (__app_major, rev_count.strip(), __app_stage)

[q2dg]

If this issue isn't resolved, this project is dead

[cmmorrow]

Hey @q2dg , I'll see if I can add py3 compatibility to this project.

[deadbits]

Hey all,

I will happily merge any PRs for Py3 compatability and I definitely appreciate the interest in this project. Unfortunately I haven't had much time to activately maintain this- I hope this changes in the near future, but anything I can do to facilitate support here let me know

[cmmorrow]

Starting on this now. I'll keep everyone updated on the status.