If I was your client I'd be pissed that you decided to rewrite my code into a legacy version of Python. Make no mistake: Python 3 is the future of Python. There will be no version 2.8 and there is no going back to 2.7.
Also, I don't know what you mean by "Amazon only supports 2.7" because boto (the main client for Python) has supported Python 3 for 2 years now. Perhaps you mean Lambda?
+1. Also it's easy to write code that supports both, so if you really need python 2 support right now (surely AWS Lambda python 3 is coming soon, you can already use it unofficially) that's a much better option than being entrenched in python 2 (mainly the string handling is the issue for buggy code that'll run in 2 but not 3).
Re:Why I'm Making Python 2.8
by paulddraper on Saturday December 10, 2016 @01:22PM
(#13147019)
He means Lambda.
Could you tell us which libraries you want don't support 3.x?
Genuinely curious as i thought nearly all of the main ones were ported now
At this point, if a library I wanted to use didn't support 3.X, I would take that as a giant red flag not to use said library.
Breaking it down to microservices, could you not have some parts as 2.7, like any that need a specific library that does not have Python 3 support, and some in 3. Or for that matter GO, or RUST?
We would look very closely at a Python 2.8, if it existed.