7 ms·
I didn't realize how bad it was until I recently looked into doing a Python Qt application. There's two competing Python language bindings for Qt: PyQt and PySi
by the_biot 2y ago
I didn't realize how bad it was until I recently looked into doing a Python Qt application. There's two competing Python language bindings for Qt: PyQt and PySide. The latter appears more free and active, so that seemed the way to go.
They have a compatibility matrix. It's mostly red.
https://wiki.qt.io/Qt_for_Python#Python_compatibility_matrix https://wiki.qt.io/Qt_for_Python#Python_compatibility_matrix
How do you even make your stuff dependent on/broken with specific Python versions? I mean how in hell?
The fact that venv is so widely used in Python was always an indication that not all was well dependency-wise, but it doesn't seem like it's optional anymore.
- twic 2y agoMy guess would be that because it's an integration with a sprawling native library, there is a lot of code which touches Python's own C API. That is not entirely stable, and it has a lot more source stability than binary stability: https://docs.python.org/3/c-api/stable.html https://docs.python.org/3/c-api/stable.html As time passes, it makes sense to support only recent versions of both Qt and Python, hence that matrix.
- d0mine 2y agoAll I see is that newer library versions drop support for old Python versions (seems natural, unless you have unlimited resources). For example, If you need Python 2 support, use corresponding old versions.