2 ms·
I'm starting to think that if a library won't switch to Python 3 then it's time for the library to die and people move on to a new library that offers similar f
by jlarocco 14y ago
I'm starting to think that if a library won't switch to Python 3 then it's time for the library to die and people move on to a new library that offers similar functionality and does work on Python 3.
For example, PIL doesn't support Python 3, but there's a GraphicsMagick wrapper [1] which does. Graphics Magick is more functional anyway.
You may have time invested in PIL and other Python 2 libraries, but newbies don't, and there's no reason to start them off on a dying version of the language. It's contributing to the chicken and egg problem that's holding Python back.
[1] https://pypi.python.org/pypi/pgmagick/0.5.5 https://pypi.python.org/pypi/pgmagick/0.5.5
- randuser 14y agoMost widely-used libraries have not actually switched to Python 3, they just support it using 2to3. Someone who only knows Python 3 would have a hard time hacking on the source code of most libraries.