5 ms·
I think the main reason was a lack of agreement between the community and the language maintainer(s) (see: Guido the BDFL). I highly doubt something like this w
by Cyph0n 9y ago
I think the main reason was a lack of agreement between the community and the language maintainer(s) (see: Guido the BDFL). I highly doubt something like this would have happened if the community had been involved. The language maintainers themselves have clarified that introducing breaking changes was a mistake in hindsight and that it will never happen again.
Anyways, the fiasco is over and Python 3 has emerged as the victor, so there really is no use discussing the issue anymore imo.
- actuallyalys 9y ago>The language maintainers themselves have clarified that introducing breaking changes was a mistake in hindsight and that it will never happen again. What are you referring to? I haven't heard or read any core developers say anything close to 'introducing breaking changes was a mistake in hindsight'.
- Cyph0n 9y agoI recall reading something along those lines, but I could be mistaken!
- Macha 9y agohttps://opensource.com/life/14/9/why-python-4-wont-be-python-3 https://opensource.com/life/14/9/why-python-4-wont-be-python...
- actuallyalys 9y agoThere's a big difference between 'Python 3 was a mistake' and 'we won't make Python 4 like Python 3'. This article is saying the latter (and implicitly argues against the former).
- makk 9y ago100% sure I read that from one of the core devs but cannot find the reference.