Parents (Total: 4)
The searched file hash is included in 4 parent files which include package known and seen by metalookup. A sample is included below:
| Key |
Value |
| MD5 | 520CED3ED0204931347E80D6E6952E75 |
| PackageArch | noarch |
| PackageDescription | QtPy (pronounced 'cutie pie') is a small abstraction layer that lets you
write applications using a single api call to either PyQt or PySide.
It provides support for PyQt5, PyQt4 and PySide using the PyQt5 layout (where
the QtGui module has been split into QtGui and QtWidgets).
Basically, you write your code as if you were using PyQt5 but import qt from
`qtpy` instead of `PyQt5`. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | python3-QtPy |
| PackageRelease | lp150.1.1 |
| PackageVersion | 1.4.1 |
| SHA-1 | FABA730B1A078B03CBD39A9D9383AB7079AD6B8D |
| SHA-256 | 5B10EE60428360127A6C7248DFDD5D4DC4F9D11657360BD198607B2CC07A6C1A |
| Key |
Value |
| MD5 | 70E90835E5D3DCB9EB5BC089BF2D17DF |
| PackageArch | noarch |
| PackageDescription | QtPy (pronounced 'cutie pie') is a small abstraction layer that lets you
write applications using a single api call to either PyQt or PySide.
It provides support for PyQt5, PyQt4 and PySide using the PyQt5 layout (where
the QtGui module has been split into QtGui and QtWidgets).
Basically, you write your code as if you were using PyQt5 but import qt from
`qtpy` instead of `PyQt5`. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | python2-QtPy |
| PackageRelease | lp151.2.2 |
| PackageVersion | 1.4.1 |
| SHA-1 | 003F1AF286F123BD151CE4CE7DBA0DDEBEFBF75B |
| SHA-256 | 6DF2AFC11A6E4F1379935801D9EA9709C6E26A89B58BC6B83ABD23401953D45C |
| Key |
Value |
| MD5 | C64526C0B7B2E778F93F2A9D1823545D |
| PackageArch | noarch |
| PackageDescription | QtPy (pronounced 'cutie pie') is a small abstraction layer that lets you
write applications using a single api call to either PyQt or PySide.
It provides support for PyQt5, PyQt4 and PySide using the PyQt5 layout (where
the QtGui module has been split into QtGui and QtWidgets).
Basically, you write your code as if you were using PyQt5 but import qt from
`qtpy` instead of `PyQt5`. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | python2-QtPy |
| PackageRelease | lp150.1.1 |
| PackageVersion | 1.4.1 |
| SHA-1 | 285249F311625F892FEDFD6442C36168C550F978 |
| SHA-256 | 5F62F8AFADCFA19D0A96337D5603955E18EE9B74D091B0EA3B9C59BD71F52267 |
| Key |
Value |
| MD5 | BBDBC004C932BB046FABE07089049A29 |
| PackageArch | noarch |
| PackageDescription | QtPy (pronounced 'cutie pie') is a small abstraction layer that lets you
write applications using a single api call to either PyQt or PySide.
It provides support for PyQt5, PyQt4 and PySide using the PyQt5 layout (where
the QtGui module has been split into QtGui and QtWidgets).
Basically, you write your code as if you were using PyQt5 but import qt from
`qtpy` instead of `PyQt5`. |
| PackageMaintainer | https://bugs.opensuse.org |
| PackageName | python3-QtPy |
| PackageRelease | lp151.2.2 |
| PackageVersion | 1.4.1 |
| SHA-1 | B0D65FB5F1EB92FAE6FD82EC6B9DCD50A9FDB0E0 |
| SHA-256 | 3AD094B8E5677C0F13E55101480FDD2F733FF000198DC6994A9B4E3483AB64AC |