3 ms·
Its 2017. After python 3.6, I hope the debate btw python2 vs 3 is put to an end.
by ram_rar 9y ago
Its 2017. After python 3.6, I hope the debate btw python2 vs 3 is put to an end.
- Kagerjay 9y agoI can't believe this is still a discussion, python 3 already practically every python 2 library http://py3readiness.org/ http://py3readiness.org/
- pfranz 9y agoIn general, Python 3 should have been what you start with for the past few years. In visual effects most of our apps have an embedded Python runtime. Those apps have a lot of internal code built around Python2 in addition to clients that have a decades worth of Python2 infrastructure. Everyone needs to move at the same time (and it's been hard even with minor versions of Python). As an industry, we're only now talking about migrating to Python 3 in 2019: http://www.vfxplatform.com/ http://www.vfxplatform.com/ Looking around, most people I worked with just do what they're told and have probably never seen Python3 yet. The past few years the industry has pushed off Python3 because of other large changes requested for third-party apps: new versions of C++, gcc, boost, Qt. It's actually been kind of tough to use Python 2 for the past couple years. I noticed the PyCon talks are a lot less relevant because they're all Python 3 oriented. Python bindings for Qt are a lot more difficult because of the old compiler used for Python 2 on Windows. I wonder how many other industries are similarly stuck?
- ltaaug8 9y agoI stopped reading there. In fact, I'm finding more and more libraries written for Python 3 exclusively, or for which Python 2 support has been discontinued. Stating "you may find a lot of packages that only support Python2" makes me think the author is just spouting off random things he's heard.