

Thus, we probably wouldn't have to support 5.11.0 and 5.11.1 if there's a good reason we don't want to.
Debian stretch install pyqt5 upgrade#
While 18.04 is still supported until 2023 by Canonical, I don't think it's as much as a blocker after an upgrade path is available and a couple of months have passed. This is getting superseded by Ubuntu 20.04 LTS in April. The obvious blocker for Qt 5.9 support is Ubuntu 18.04 LTS.When requiring PyQt 5.11, we can also go back to importing PyQt5.sip rather than either sip or PyQt5.sip.Given that Debian Stable (Buster) ships Qt 5.11, support for that should probably still stay for a while.But (almost) everyone using the newest release also has its benefits. Still less effort than keeping support around, it seems to me. Keep using v1.2.x, possibly with us backporting some bugfixes there.install qutebrowser via tox - however, that seems to have some weird TLS issues on Debian stable, so it might not be a working alternative. Originally I wanted to keep support around until the next Debian stable, but since that's somewhen in early/mid-2019, that's really not realistic. Qt.KeyboardModifiers (and probably other flags) is unhashable (which means a custom hash method was needed for KeyInfo).qutebrowser -version segfaults on exit with PyQt 5.7.Debian is explicitly not interested in keeping it secure - they'd rather keep an old buggy version and never ship security fixes, so at some point it's really unreasonable to continue using qutebrowser there 😟.It starts to get an issue with various pages - it looks like GitHub just broke again, and this time it's not fixed by changing the UA.It crashes outright on newer distributions without disabling the seccomp sandbox ( #3163).Features like printing or spellchecking aren't supported by Qt.spent a lot of time to get GreaseMonkey scripts running there, and even for ongoing changes to GreaseMonkey support it's a pain (it's essentially like having to handle three backends).
Keeping Qt 5.7 support (and thus, support for running qutebrowser with a system-installed Qt on Debian stable) is turning out to be more and more of an issue:
