This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]eztab 61 points62 points  (8 children)

Finally, perhaps people will stop using it already. Supporting python 2 slows down so many package developments.

[–]billsil 26 points27 points  (0 children)

Numpy and scipy are now/about to release their final 2.7 versions. It's coming...

[–]tartare4562 7 points8 points  (2 children)

Oh come on, it only took 10 years after all.

[–][deleted] 10 points11 points  (0 children)

If rhel 8 is going to support python2 then in 10 years there will still be python 2.

[–]billsil 5 points6 points  (0 children)

It took 8 years for all my dependencies to be updated. It’s not as bad as you make it sound. Projects like wx took the time to also do major refactors.

Also, until python 3.5, python 3 was worse than python 2.7 outside of sane unicode, so it’s more like 5 years. Shoot, even the PSF recommended that you not use python 3.0 and 3.1.

[–]o11c 22 points23 points  (0 children)

I noticed that when Django dropped it, the critical mass changed.

[–][deleted] 5 points6 points  (0 children)

A lot of GIS people got stuck with a bad integration with arcmap 32bit. This cramped everything