You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The userExportedAttributesUI python file is trying to import QStringListModel from PySide2.QtGui. On PySide2 I found that this class in fact lives in QtCore instead.
Steps to reproduce the behavior:
Open any version of Maya using PySide2, open Script Editor
Run the following code in a python tab:
from pxr.UsdMaya import userExportedAttributesUI
This code yields the following error:
# Error: ImportError: file /.../plugin/pxr/lib/python/pxr/UsdMaya/userExportedAttributesUI.py line 52: cannot import name QStringListModel #
SPECS -
Linux CentOs 7 x64
Maya 2020
The text was updated successfully, but these errors were encountered:
I was able to reproduce this in PR114 with the Pixar plug. I think this one is definitely specific to the pxr plug-in. Maya USD doesn't contain userExportedAttributesUI from what I can see. Will speak with the team to see what we can do about this issue.
it's worth giving a try on this with an older build that hasn't updated Qt to confirm.
harveyr-gh
changed the title
userExportedAttributesUI | cannot import name QStringListModel
[MAYA-102675] userExportedAttributesUI | cannot import name QStringListModel
Jun 3, 2020
Hi @mhamid3d, thanks for reporting this, and sorry it has languished so long. It somehow managed to slip by me earlier this year, and we've not yet tried to use this UI with Maya 2020+ which is where it starts to appear, so we hadn't tripped over it yet.
The
userExportedAttributesUI
python file is trying to importQStringListModel
fromPySide2.QtGui
. On PySide2 I found that this class in fact lives inQtCore
instead.Steps to reproduce the behavior:
This code yields the following error:
# Error: ImportError: file /.../plugin/pxr/lib/python/pxr/UsdMaya/userExportedAttributesUI.py line 52: cannot import name QStringListModel #
SPECS -
The text was updated successfully, but these errors were encountered: