Re:Numpy: Plan for dropping Python 2.7 support
by icebraining on Thursday November 16, 2017 @05:31AM
(#15711579)
I was responding to "keeping it backward-compatible", which it did not do. In any case, Python 3 is not exactly a brand new language, many codebases can be adjusted to run on both engines without much effort. I don't think the difference is as stark as you've painted it.
Re:Numpy: Plan for dropping Python 2.7 support
by collinmanderson on Thursday November 16, 2017 @07:44AM
(#15712201)
On the other hand, there’s still a lot of code that needs porting. See http://portingdb.xyz
Re:Numpy: Plan for dropping Python 2.7 support
by speedplane on Thursday November 16, 2017 @05:37AM
(#15711605)
> without much effort
It's an enormous amount of effort. It's been a decade and the end is nowhere in site. Python 3 is a tragedy.
You can run PHP3, PHP4 and PHP5 projects with little or no change at all, code dating back to 1990s with PHP7. If you cared a bit and adjusted your code over the years, most changes are announced many versions ago and got deprecated. E.g the original MySQL API had been deprecated for a decade or so years, and only got removed with v7, yet it's easy to update the code to the newer APIs, as it was possible since early 2000s, when the newer API got introduced and stayed unchanged since then. And you could use a shim too.
PHP and Java (and several other languages) have really kept an eye on backwards compatibility, you cannot deny that or paint it in another light.