0.5.0

Alpha release of --convert for Qt Designer files.

Steps

1. Have your .ui file ready.
2. Compile your .ui file using the PySide2 uic module.
3. Convert your compiled .ui file with Qt.py

Demo

$ pyside2-uic my_ui.ui -o my_ui.py
$ python -m Qt --convert my_ui.py
# Creating "my_ui_backup.py"..
# Successfully converted "my_ui.py"

Note to Maya 2017-users: You can find pyside2-uic in your Maya installation directory

Implementation

The method at which the conversion happens is early alpha and is expected to work in common cases, but may not cover all edge cases.

What we need is for you to test this, and let us know where it fails so we can repair it.

The implementation will, at this point in time:

1. Replace occurrences of from PySide2 import with from Qt import
2. Replace occurrences of QtWidgets.QApplication.translate with Qt.translate

And that's it.

The function is idempotent and will create a backup of your original, as my_ui_backup.py

• Reference
• Documentation

Let us know what you think!

0.4.3

• Implements #137

Disable run-time validation of attribute overrides, safe those for tests.

If you've experienced issues where Qt.py is telling you it tried overriding an existing attribute..

AttributeError: Cannot override existing name: PySide.QtWidgets # 
# Error: AttributeError: Cannot override existing name: PySide.QtWidgets # 

Then this one's for you.

It maintains the safety of ensuring no original attributes are overridden, while at the same time enabling further flexibility for the users.

Enjoy!

0.4.2

Added compatibility with custom distribution of PyQt5, https://github.com/pyqt/python-qt5.

0.4.1

Added support for importing widgets directly from QtWidgets with bindings for Qt 4.

from Qt.Widgets import QPushButton

0.4.0

This release includes guards against problems related to co-existence.

Co-existence

Great care is taken to make sure Qt.py does not affect the original binding. This means no chances can be made to any pre-existing member.

Before, this care was made by eye. But now this care is automated and guarded against per commit, pull-request and at run-time (at minimal cost).

Theory

Notice the add and remap functions.

These replace the previous layout of remapping and adding.

# Before
PyQt4.QtWidgets = PyQt4.QtGui

# After
remap(PyQt4, "QtWidgets", PyQt4.QtGui)

By using a function as opposed to directly assigning, we lose out on readability, but gain security.

The safe=True argument is meant to facilitate times where we do overwrite, but ensure to include a full array of tests to ensure the original member has not been broken.

The Qt.__modified__ list of strings holds any members that do alter an existing member of the original binding.

Today, no member uses safe=False and __modified__ is empty as it should.

0.3.4

Changes.

• Support QtWebKitWidgets
• Repair PySide support

PySide wasn't working under some circumstances, see stack trace on Travis.

0.3.3

Added Qt.load_ui and fixed #86.

• https://github.com/mottosso/Qt.py#load-qt-designer-ui-files

0.3.1

Added support for vendoring.

myproject/
  vendor/
    Qt.py

# Absolute reference
from myproject.vendor.Qt import QtWidgets

# Local reference
from .vendor.Qt import QtWidgets

# Direct reference
from .vendor import Qt

You were able to bundle Qt.py before as well, via a slightly more awkward syntax.

from .vendor import Qt
from Qt import QtWidgets

0.3.0

This release boasts one addition and one change.

• Dockerfile included
• Qt.py no longer supports versions of PyQt4 lower than 4.7

Docker

This is for contributors to properly test their additions to the project before committing.

$ cd Qt.py
$ docker build -t mottosso/qtpy https://github.com/mottosso/Qt.py.git
$ docker run --rm -v $(pwd):/Qt.py mottosso/qtpy
# Tests require PySide and PyQt4 bindings to be installed ... ok
# Setting QT_PREFERRED_BINDING properly forces a particular binding ... ok
# Preferring None shouldn't import anything ... ok
# 
# ----------------------------------------------------------------------
# Ran 3 tests in 0.530s
# 
# OK

PyQt4 4.7 and above.

This means sip APIs are implicitly set to API v2 so as to align with PyQt5 and both PySide's. If you are using Qt.py alongside PyQt4, make sure you either import Qt.py first, or set the APIs beforehand.

import sip

sip.setapi("QString", 2)
sip.setapi("QVariant", 2)
sip.setapi("QDate", 2)
sip.setapi("QDateTime", 2)
sip.setapi("QTextStream", 2)
sip.setapi("QTime", 2)
sip.setapi("QUrl", 2)

import PyQt4

0.2.6

First automatic release on PyPI.