4 ms·
Not until the year 2015 and python 3.5 around the corner. That's when the interpreter finally got the minimum support required to make code compatible with bot
by user5994461 6y ago
Not until the year 2015 and python 3.5 around the corner.
That's when the interpreter finally got the minimum support required to make code compatible with both, and linters improved enough, and some libraries started being ported.
- pseudalopex 6y agosix 1.0 was in 2011.[1] 50% of the top 200 packages were compatible by the end of 2012.[2] And there were features you could use in 2008 to make the eventual conversion easier. [1] https://github.com/benjaminp/six/commits/1.0.0 https://github.com/benjaminp/six/commits/1.0.0 [2] https://python3wos.appspot.com/ https://python3wos.appspot.com/
- user5994461 6y agoHence the ecosystem became usable around 2015 ;) It takes time between the initial release and enough fixes/additions to become usable, and the documentation/stackoverflow to cover it.
- pseudalopex 6y agoAround 2015 is when lots of people found all their dependencies were compatible with Python 3 or abandoned and replaced. How much work they had to do depended on if they put any effort into compatibility for the last 7 years. Or even just followed recommendations for Python 2. Writing 100% compatible code wasn't practical in 2008 but distinguishing bytes from text was.
- dwheeler 6y ago> 50% of the top 200 packages were compatible by the end of 2012. Which meant you could not usually convert, since ALL dependenices had to be converted. The chance of doing that successfully then with 300 libraries (including transitive dependencies) was approximately (0.5)^300, which is practically 0.