Qtpy is non-functional with PySide 6.7.0

[trwilliams79]

Qtpy is non-functional with PySide 6.7.0

[hmaarrfk]

I came here to see if this was indeed a qtpy issue or a PySide6 issue, and it seems to in fact be some strange interaction:

Even reducing the imports to the strict minimum:

import sys
from PySide6.QtWidgets import QTreeWidget, QTreeWidgetItem, QTextEdit, QListWidget, QSplitter, QWidget, QApplication, QHBoxLayout

class Example(QWidget):

I have a feeling it might be related to: https://bugreports.qt.io/browse/PYSIDE-2675

Will continue to investigate (fyi, I'm not a developer of qtpy, just a mere user trying to help)

[hmaarrfk]

I really think it has something to do with their lazy import structure. The issue I referred to and some notes from https://wiki.qt.io/Qt_for_Python_Development_Notes hint that they are working through a few things with it.

import sys
from PySide6.QtWidgets import QWidget
from qtpy.QtWidgets import *
from qtpy.QtGui import *
from qtpy.QtCore import *

class Example(QWidget):

"works"
So I think it is related to the note:

[hmaarrfk]

So FYI, for my code, I had to add above all other qtpy wigets imports and whatnot

import qtpy
if qtpy.PYSIDE6:
     from PySide6.QtWidgets import QWidget

with an adequate note as to when it can be removed. It isn't ideal, but it "works".

[hmaarrfk]

The screenshot of their development notes indicates that * importing may be a source of problems.

This compatibility layer uses star style imports.

[ccordoba12]

@hmaarrfk, thanks for chiming in and providing additional context for this issue!

I doubt that this is a problem with Qtpy because for the most part it's a wrapper for PySide/PyQt (we patch some objects for compatibility between bindings and versions, but we try to keep that to a minimum).

[trwilliams79]

So FYI, for my code, I had to add above all other qtpy wigets imports and whatnot

import qtpy
if qtpy.PYSIDE6:
     from PySide6.QtWidgets import QWidget

with an adequate note as to when it can be removed. It isn't ideal, but it "works".

It should be noted that I'm not lazy importing in production code, just in the example. That said, I suspect the solution you provided will work. Its not ideal, but it should work. I'll have to try it out when I return to the office on Monday.

[ewerybody]

I wonder if it works again If one unrolls ALL members that would be imported via * like:

...
elif PYSIDE6:
    import PySide6.QtCore
    from PySide6.QtCore import (
        ClassInfo, MetaFunction, Property, QAbstractAnimation, QAbstractEventDispatcher,
        QAbstractItemModel, QAbstractListModel, QAbstractNativeEventFilter, QAbstractProxyModel,
        QAbstractTableModel, QAnimationGroup, QBasicMutex, QBasicTimer, QBitArray, QBuffer,
        QByteArray, QByteArrayMatcher, QCborArray, QCborError, QCborKnownTags, QCborMap,
        QCborParserError, QCborSimpleType, QCborStreamReader, QCborStreamWriter,
        QCborStringResultByteArray, QCborStringResultString, QCborValue, QChildEvent, QCollator,
        QCollatorSortKey, QCommandLineOption, QCommandLineParser, QCoreApplication,
        QCryptographicHash, QDataStream, QDate ...

(snip from qtpy/QtCore.py)

Probably. I'm not gonna try for my hobby projects (will simply deprecate PySide2 support)
But might be an idea for qtpy (and our wrapper at work)

[trwilliams79]

The screenshot of their development notes indicates that * importing may be a source of problems.

This compatibility layer uses star style imports.

Ah, my bad, I misread what you'd originally entered.