Mike Hendricks

> I assume we should avoid the `QtSiteConfig.py` mechanism so that it remains available for users to use at their site? Yeah, it's best left for the end user as...

Looks like PyQt5 requires inheriting from `QObject` not python's object to use the `Slot` decorator. This code change fixes the original example, and will run for both PyQt5 and PySide2....

I've found another inconsistency when creating a `QApplication` between PyQt5 and PySide2. PyQt5 requires passing a list, but PySide2 does not. ```py >>> from PySide2 import QtWidgets >>> QtWidgets.QApplication() >>>...

This piqued my interest, and re-affirmed why I avoid merge commits like the plague in feature branches, they make updating the history of a feature branch branch harder. The merging...

Also ensure that unicode is supported by all of HAB. Here is a test configuration. ```json { "name": "utf8", "inherits": false, "distros": [], "environment": { "set": { "UTF_VALUE": "[\ud83c\udf89]", "ASCII_VALUE":...

We could possibly add a `hab cfg` or `hab site` command that would provide a unified way to set the `HAB_PATHS` env variable. Currently, you have to use the correct...

It also would be nice to add some filter features so you can target specific aliases, etc.

Addressed by #434.

The dropping of classes like `QTextCodec` in 1.4 has already caused issues for us and I've had to resort to using the pip requirement of `Qt.py==1.3.*`.

@mottosso regarding github actions and testing, would you be open to switching from docker and .sh files to using [tox](https://tox.wiki/en/stable)? While I was working on PyQt6 support I noticed that...