The new Unicode issues in Python 3 are a non-starter for my work - if there was a definitive guide to sorting those issues out I'd seriously consider it, but judging from the low quality answers to Armin Ronacher's posts about Unicode in Python 3, it won't be any time soon.
That being said, this article is hilariously unproductive. The idea of forking Python 2 and just "taking Python 3 out back" makes no sense at all... smoothing the transition from 2 to 3, or adding killer features to 3 is the way to go. We could do with less articles like this.
2
u/justdweezil May 26 '14 edited May 26 '14
The new Unicode issues in Python 3 are a non-starter for my work - if there was a definitive guide to sorting those issues out I'd seriously consider it, but judging from the low quality answers to Armin Ronacher's posts about Unicode in Python 3, it won't be any time soon.
That being said, this article is hilariously unproductive. The idea of forking Python 2 and just "taking Python 3 out back" makes no sense at all... smoothing the transition from 2 to 3, or adding killer features to 3 is the way to go. We could do with less articles like this.