3 ms·
"The breakup between Python 2 and 3 has been very slow and painful. Python devs know that, and that's why they won't break compatibility in such big and drastic
by bootload 11y ago
"The breakup between Python 2 and 3 has been very slow and painful. Python devs know that, and that's why they won't break compatibility in such big and drastic way ever again."
Fork, don't break, cf Pillow (PIL fork) ~ http://python-pillow.github.io/ http://python-pillow.github.io/
What are the most commonly used Py2 packages that need to be Py3?
- jacobolus 11y ago> What are the most commonly used Py2 packages that need to be Py3? https://python3wos.appspot.com https://python3wos.appspot.com http://py3readiness.org http://py3readiness.org
- nerdwaller 11y agoFor most of the ones that aren't compatible I've found an alternative or monkey patched a method to support python 3 (I'm looking at supervisor -> circus and flask-session -> monkey patch because the author seems to have abandoned it).
- Siecje 11y agoFor me it's supervisor and beanstalkc and fabric but you can run your fabric scripts with Python2 easily enough.
- brownbat 11y agoPaiMei was a pretty good toolkit, but it doesn't even work with anything after 2.4, at least not out of the box. So maybe that's not even an example of the 2/3 split, it's just old.