2 ms·
Or all the people maintaining large python in house projects that had a certain expectation of how many people it takes to maintain a mature largely finished pr
by lanstin 4y ago
Or all the people maintaining large python in house projects that had a certain expectation of how many people it takes to maintain a mature largely finished project which is suddenly much higher. I supported our framework adding a feature here and there, on boarding a new app team here and there for like 10% of my time. To switch it all to Python 3 would have been major work, high risk, and no real benefit. We either still run Python 2 now, or have migrated to Go (slightly more verbose code and slightly slower dev time, for much lower compute foot print).
To be fair it was a place where the Python fans advocated for its use but to management was always a bit skeptical, so we had to make it all seem easy. We had good solutions to internationalization which all broke with Python 3.