4 ms·
So ignoring the hype, here's the outcome-to-date... The ticket was reconsidered, reopened and classified as a bug. http://bugs.python.org/msg212771 http://bugs
by tomchristie 13y ago
So ignoring the hype, here's the outcome-to-date...
The ticket was reconsidered, reopened and classified as a bug.
http://bugs.python.org/msg212771 http://bugs.python.org/msg212771
Nick Coghlan's dissection of the issue here: https://mail.python.org/pipermail/python-ideas/2014-March/026647.html https://mail.python.org/pipermail/python-ideas/2014-March/02... is pretty much perfect - wonderful piece of technical writing!
Donald Stufft has expressed an interest in making the patch for this happen, and assuming all goes as planned this usage will raise a deprecation warning in 3.5 and be fully fixed in 3.6.
News in brief: User raises issue. Issue gets resolved.
- sanderjd 13y agoNeat! This stuff actually works sometimes!
- Grue3 13y agoWill 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.
- scrollaway 13y agoWow. This "Mark Lawrence" guy is absolutely worthless. I googled him and cannot believe the Python community still has guys like him.
- mixmastamyk 13y agoI took a look and yes, this is the kind of guy that results in a system with a hundred weird exceptions that have to be memorized.