4 ms·
Will it be resolved in 2.x though? That's what most people care about.
by Grue3 13y ago
Will it be resolved in 2.x though? That's what most people care about.
- dtech 13y ago2.x is EOL and only remains for legacy programs. A backwards-incompatible change won't even be considered for this branch.
- username223 13y agoMy guess is that eventually someone with enough money on the line will be sufficiently harmed by the Python 3 nonsense to maintain 2.x, at which point obvious bugfixes like this will be "ported" (it's probably a 2-line change).
- Perseids 13y ago> That's what most people care about. I'll make an equally aggressive counter point: Dammit guys and gals, stop using 2.x. Python 3 came out more than 6 years ago. You are holding back and splitting the community. And if you tell me 3.x has no perceived value then this is the value that is slowly stacking up.