-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't work with Nuke #301
Comments
Tests:
I presume it is some Nuke's internal incompatibility issue with outside python3 PyQt5 but that is just a guess. |
What Nuke version? I've opened the Pyblish QML GUI in Nuke no problem in Linux in the past. |
Hi @darkvertex thanks for question. Its windows 11.2v3. Would you mind to share your config? |
It's studio stuff using Rez packages that I can't really share, sorry, but it should be possible to accomplish a working pyblish-qml with a conda environment with only Python 2.7, PyQt5, pyblish-base and pyblish-qml and using the It can be a shellscript/.bat that sets the good environment and passes the args straight to the python executable, it doesn't necessarily have to be a path to python.exe itself. |
@jezscha Have you experienced the issue on a different computer or user? Could it be something pre-existing in your particular environment? E.g. multiple Qt installs? |
@darkvertex I understand. But anyway thanks for the comprehension. In our setting we wish to stick to Python3.6.5, PyQt5==5.7.1 for all integrations if it would be possible. I understand Pyblish-qml in Nuke can be accomplished in Python2.7 and I have already experienced it myself. @mottosso I have been testing it on two machines which one of them was vanilla and no paths existed in env-vars. Also the second has been cleaned from all traces in env-vars and files and register. I am going to test it on other tomorrow so lets see. |
@jezscha were you able to make progress with this the way you wanted? |
As reported by Jakub over in the chat, there's something preventing Pyblish QML from working with Nuke.
The text was updated successfully, but these errors were encountered: