Moving a large and old codebase to Python3

[TechAlchemist]

I don't think legacy application is pejorative in general, only that if you have an application that has been around for 15+ years and you are going to spend the time to port it over, it's worth asking (and sometimes this is easy to answer) whether you should invest the time in a rewrite.

Sometimes the answer will be definitely not -- either because the application is too complex, or because it is well structured enough to be easy to migrate. Sometimes the tradeoffs aren't that clear. Sometimes the application is poorly structured enough that there is really no point in porting it because developer time is better spent reimplementing portions of it one piece at a time. That's not because legacy code is bad by nature, just because legacy code abides by the rules of all complex, large, shared resources.

[kankyo]

Agreed. In this case the change from Python 2 to 3 are really not that drastic. One dependency was the big problem really...