This switches to importing Qt classes via the qtpy abstraction layer. The library will then use which ever Qt binding you have in your environment. If you have multiple, its possible to select one using an environment variable (see https://github.com/spyder-ide/qtpy).
A small change to some mocking in a test was needed.
This passes all the tests, but has not been tested for an application that uses the library.
An application that uses eqt, will now need to add a dependency on the Qt binding that it wants to use.
Closes #2
This switches to importing Qt classes via the qtpy abstraction layer. The library will then use which ever Qt binding you have in your environment. If you have multiple, its possible to select one using an environment variable (see https://github.com/spyder-ide/qtpy).
A small change to some mocking in a test was needed.
This passes all the tests, but has not been tested for an application that uses the library.
An application that uses eqt, will now need to add a dependency on the Qt binding that it wants to use.