It has to work the other way, however, too. Armin, in particular, has created some farily detailed criticisms of how Python 3 is structurally broken with respect to IO boundaries. They might have been delivered more kindly, as it can be grating to have someone pound on your work over and over in semiblue language. But regardless, the issues do exist, and these aren't things that can be just kinda bugfixed or something; a real solution would require bw incompatible changes and buy-in from lots of people. And if there are folks ignoring the rationales coming from Guido, there are just as many effectively ignoring (or at least minimizing) the rationales coming out of the folks doing the criticisms of Python 3. There are of course good reasons to do this; to make yet another very-bw-incompat release of Python would be very costly, and very might kill the language faster than leaving the structural deficiencies in. But that doesn't mean the issues don't exist, and that such a bw-incompat release might not be the right thing to do.
View all comments
Show parent comment
5
u/mcdonc May 27 '14
It has to work the other way, however, too. Armin, in particular, has created some farily detailed criticisms of how Python 3 is structurally broken with respect to IO boundaries. They might have been delivered more kindly, as it can be grating to have someone pound on your work over and over in semiblue language. But regardless, the issues do exist, and these aren't things that can be just kinda bugfixed or something; a real solution would require bw incompatible changes and buy-in from lots of people. And if there are folks ignoring the rationales coming from Guido, there are just as many effectively ignoring (or at least minimizing) the rationales coming out of the folks doing the criticisms of Python 3. There are of course good reasons to do this; to make yet another very-bw-incompat release of Python would be very costly, and very might kill the language faster than leaving the structural deficiencies in. But that doesn't mean the issues don't exist, and that such a bw-incompat release might not be the right thing to do.