PyQt4 to PyQt5 Conversion Script

[mark.mc...@disneyanimation.com]

At Walt Disney Animation Studios we have been hard at work converting our code to Qt5/PyQt5 for CY2016. One of the key components in our conversion process was a PyQt4 to PyQt5 Conversion Script from a github project known as pyqt4topyqt5. We have greatly enhanced this script and our changes are now available on github. Thanks to Riccardo Ferrazzo for starting this project. It has been a great help to us and I hope that it will be a great help to others as well.

We will be giving a brief overview of our experiences with the Qt5/PyQt5 conversion process at the "VFX Reference Platform - A Common Target for Building VFX Software" Birds of a Feather at SIGGRAPH 2016.

[Francois Chardavoine]

Thanks for getting your changes posted back to the community: this will be very useful for anyone transitioning a lot of pyqt code.

Maybe post-siggraph it would be useful to post back to this thread with a summary of gotchas or cases that weren't handled automatically by the script, and strategies you may have taken to streamline the conversion process.

Francois.

On Tue, Jul 19, 2016 at 9:50 AM, <mark.mc...@disneyanimation.com> wrote:

At Walt Disney Animation Studios we have been hard at work converting our code to Qt5/PyQt5 for CY2016. One of the key components in our conversion process was a PyQt4 to PyQt5 Conversion Script from a github project known as pyqt4topyqt5. We have greatly enhanced this script and our changes are now available on github. Thanks to Riccardo Ferrazzo for starting this project. It has been a great help to us and I hope that it will be a great help to others as well.

We will be giving a brief overview of our experiences with the Qt5/PyQt5 conversion process at the "VFX Reference Platform - A Common Target for Building VFX Software" Birds of a Feather at SIGGRAPH 2016.

--
You received this message because you are subscribed to the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vfx-platform-dis...@googlegroups.com.
To post to this group, send email to vfx-platfo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/be711b3f-5417-4449-8cbe-aeebb71f793b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Marcus Ottosson]

Possibly relevant, we are working towards a similar goal, establishing and accounting for differences between the two. But rather than choosing either or, we've made a shim so as to support both at once. One of the goal is to enable this very same transition from Qt 4 to 5, which we expect will need backwards compatibility for at least a few years. Another is to simply not bother choosing to begin with, for new projects.

- https://github.com/mottosso/Qt.py

To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CADBZUEhi_fHNjVzV8%2Bgo-Lt_XC2sqydjEAnhUi5xkHuh0_njuQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Marcus Ottosson
konstr...@gmail.com

[Mark McLaughlin]

Yes, we are aware of Qt.py and are also looking into using it as well (for the reasons you mentioned).

You received this message because you are subscribed to a topic in the Google Groups "vfx-platform-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vfx-platform-discuss/LzGEKXdXp6w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vfx-platform-dis...@googlegroups.com.

To post to this group, send email to vfx-platfo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vfx-platform-discuss/CAFRtmOBxp0sNrP-FebgGPfiRhB%3DXqEG7Qq1adEr__vxPC8iQqA%40mail.gmail.com.

[Joshua LaCross]

I get the error "can't open file 'pyqt4topyqt5.py" I don't see any file in the directory called " pyqt4topyqt5.py" but the instructions say that's what I should be calling