2 ms·
> Having worked in python for about a decade, first in python2 and lately in python3, and having seen projects convert, I find this article baffling. I found S
by the_mitsuhiko 7y ago
> Having worked in python for about a decade, first in python2 and lately in python3, and having seen projects convert, I find this article baffling. I found Six to work pretty well, and where it didn't it wasn't hard to change.
It matters a lot where you work. If you are in high level land Python 3 is not much of a chance. If you work at the boundary (wire protocols, OS interop, text transformation) then Python 3 is a significant step back, especially before 3.6. A lot of the mud that Mercurial stepped through is also where I went through with my libraries. The day I managed to get the PEP through that reintroduced the u prefix on strings was also the last time I voluntarily participated in a language summit. The atmosphere was awful and not evidence based.
- Jasper_ 7y agoYeah, I was around for the sidelines of PEP-461, reintroducing % onto the bytes type, trying to get things done behind the scenes, and it was just a miserable experience all around. I don't think anybody cared to understand our concerns about why we should bother making the bytes type useful. At times it seemed like they believed leaving in the concatenation on the bytes type was a mistake. Read through the receipts here: https://bugs.python.org/issue3982 https://bugs.python.org/issue3982
- the_mitsuhiko 7y agoA lot of present day Python 3 programmers also have not been part of the very emotional conversations about getting some of these things back in the early days of Python 3.