Mike Hendricks

I haven't done any Qt5 only code yet, but it makes sense to separate it from Qt.py for when you want to take advantage of the new features. I think...

What about using both Qt.py and QtX.py modules? ```python from Qt import QtCore, QtWidgets from Qt5 import QtMultimedia, QtQml ``` Qt5.py would just cover the Qt 5 only parts of...

Unless I'm missing something, I don't think they are technically needed because the duplication is in the key, value per binding. ie, we are trying to map the source to...

That makes sense, I was thinking of it from the perspective of QtPrintSupport. Everything in that is a common member with the same name, just located under different modules. It's...

`Qt.QtCompat.QFileDialog` already provides a compatibility specifically for the PyQt4 static members `getOpenFileName`, `getOpenFileNames` and `getSaveFileName` return not matching the other bindings. It should be possible to implement a method for...

I was going to say number 2 would be easy to implement by adding a QtCompat namespace decorator using the code in `_pyside2_qtcore_qsocketnotifier` for PySide2 only, but then I realized...

https://github.com/mottosso/Qt.py/blob/master/Qt.py#L1000 hmm. I wonder if the existing `_build_compatibility_members` would work. It's pretty generic, and wonder if adding a "__new__" key to the `_compatibility_members` dict would be all that is needed....

That's too bad. Does anyone have experience with managing PySide2 memory? Also, socket.socketpair, socket.AF_UNIX, and socket.fromfd are only available on unix.

I think QtCompat is going to grow a lot if we add more support for obsolete members, and there are other issues like changed return values that will need to...

Qt4: ```cpp QPixmap QPixmap::grabWidget(QWidget * widget, const QRect & rectangle) QPixmap QPixmap::grabWidget(QWidget * widget, int x = 0, int y = 0, int width = -1, int height = -1)...