4 ms·
Even ignoring the lib issue, there were major performance regressions. Py3 didn’t really become clearly better until at least 3.4.
by TylerE 7y ago
Even ignoring the lib issue, there were major performance regressions. Py3 didn’t really become clearly better until at least 3.4.
- melling 7y agoThat was 5 years ago. I don’t do a lot of Python, and have been exclusively using v3, but I thought you could make your Python 2 somewhat compatible with v3 by using libraries, etc. How close can you come to a Python code base that runs in v2 and v3?
- joshuamorton 7y ago> How close can you come to a Python code base that runs in v2 and v3? Using the `six` module, this is (nearly) trivial for 99% of code. If you're doing certain weird things, its more difficult but possible. (I say this having done py2-3 conversion or dual support for lots of vanilla code, as well as a significant amount of weird code: c/c++ extensions and code that uses advanced features like code object introspection and dynamic imports/rewriting/etc).
- tingletech 7y agoI have some libraries I maintain with `six` -- I find it like writing in a whole new dialect (neither 2 nor 3). I moved to futurize for some libraries -- its like writing python 3 that will run on python 2. I am looking forward to dropping python 2 support on libraries I maintain.
- TylerE 7y agoThe problem is when your devs are spending 100% of time, or close to it, on work clients are paying for, it's really hard to spend time porting. Porting isn't really as trivial as you make it sound, either.
- tingletech 7y agoIf it ain't broke, why fix it?
- TylerE 7y agoPretty much.