9 ms·
Python didn’t have a single big player like Rails to “lead the charge”. Instead, its ecosystem is made up of many smaller libraries. Because it’s not possible
by pansa2 6y ago
Python didn’t have a single big player like Rails to “lead the charge”. Instead, its ecosystem is made up of many smaller libraries.
Because it’s not possible to run Python 2 and Python 3 code together, none of those libraries could upgrade until its dependencies had done so. This just led to everyone waiting for everyone else.
- xapata 6y agoPoint 2 is False. It's easily possible to write code compatible with both 2 and 3. It's becoming less pleasant as one can't take advantage of the great new features from v3.6+, but I've done that for about a decade now. I agree somewhat with Point 1, but the Python ecosystem is larger than Ruby's. Each domain could have moved separately, and did, to some extent.
- pansa2 6y agoSorry, I meant that Python 3 code can’t use dependencies that are written in Python 2. Therefore a library couldn’t upgrade to Python 3 until all its dependencies had upgraded.