3 ms·
I refused to get involved in 2to3 migration projects for years. I recently took care of a 2to3 migration involving a popular web framework and a few technologi
by mkl95 5y ago
I refused to get involved in 2to3 migration projects for years.
I recently took care of a 2to3 migration involving a popular web framework and a few technologies for one of my employer's clients. The codebase is large and convoluted but I still found it surprisingly easier and way more interesting than I expected.
There is some actual difficulty in dealing with packages that have deprecated for years, and other gory details. But these days 2to3 drama is mostly a meme. The Python community, with a few exceptions, has done an amazing job at keeping things working.
- stuaxo 5y agoI've done this for a few upstream projects. If you want have a bug you want attention on in an upstream project, the easiest way to get it is to do a task for them first, and doing python 2 to 3 is a usually a pretty straightforward one.