Python 2 to 3 was genuinely painful for anyone maintaining large codebases in 2019. The string encoding differences alone broke entire pipelines, and the fact that so much enterprise software hung on for years past EOL proves the migration cost was real, not imagined. Communities that laugh at ‘still on Python 2’ ignore that rewriting mature codebases is not a weekend project.
Python 2 to 3 was genuinely painful for anyone maintaining large codebases in 2019. The string encoding differences alone broke entire pipelines, and the fact that so much enterprise software hung on for years past EOL proves the migration cost was real, not imagined. Communities that laugh at ‘still on Python 2’ ignore that rewriting mature codebases is not a weekend project.