On Sat, 4 Nov 2017, Chris Burel wrote: > I think this is a remarkably short sighted statement. It assumes that people > that would use these bindings have no existing Python codebase at all, and > can afford to start a brand new project. The reality is much different. > > Let's take a specific example. I have 6 years experience writing Python for > the visual effects industry. We have a 10 year old Python 2 codebase. We also > use an application from Autodesk called Maya. It has been a Qt 4 application > with Python 2 embedded since 2012. In 2016 they jumped to qt 5 and pyside2. > Now Autodesk knows that companies have built large codebase around their > product that requires Python 2. What would've happened if pyside2 did not > support Python 2.7? They'd be stuck either forcing all their customers to > move to Python 3 and risk people not wanting the new version of the software, > or they'd be prevented from moving to Qt 5. >
You will have to switch to Python 3 by 2019, since that's what the VFX Reference Platform says. If you haven't started on the migration yet, you're very late. And the VFX Refernece Platform is basically Autodesk telling the rest of the industry what to use, including their weird patchset for Qt... > So no, Python 2 is not dead. Not by a long shot. For VFX, it will be dead in 2019. See http://www.vfxplatform.com/ -- Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org
