<div dir="ltr">Florian,<div><br></div><div>Thanks to provide those wiki docs as well as the qt releasing mailing list, they're definitely</div><div>helpful indeed to make proper planning.</div><div><br></div><div>If I look in retrospective is funny though, that QTBUG-74492 is the first one I've ever been involved with, </div><div>this bug was opened in 21.03.2019 and after few months passed nobody was working on it or they didn't</div><div>know what the problem was. I decided to spend some days bisecting the bug and finding the root cause </div><div>of the problem, thanks to that the author who introduced the bug in the first place could fix it properly in few days. In any case, </div><div>finding the issue was really tricky and the fix ended up to be quite "trivial" one. The moral of the story here is, </div><div>for something as trivial as this one you'll need to wait quite a lot of time to get</div><div>a proper release... and that's assuming you're interested enough to help Qt team to narrow it down. The </div><div>workload of Qt devs isn't small neither... which indicates there is room to optimize development in that company.</div><div><br></div><div>Bug opened in 21.03.2019 and official release with the fix delivered in 15.08.2019... That's quite a lot<br></div><div>of time to wait for...</div><div><br></div><div>Anyway, at this point a global view of how things work in both Qt & pyqt has become +/- clear, which is great so you</div><div>know what you can or can't expect.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 20, 2019 at 3:10 PM Florian Bruhin <<a href="mailto:me@the-compiler.org">me@the-compiler.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, Jul 20, 2019 at 02:53:29PM +0200, BPL wrote:<br>
> Anyway... I'll try again to see if I can make it work but hopefully a new<br>
> pyqt wheel with this annoying bug fix<br>
> <a href="https://bugreports.qt.io/browse/QTBUG-74492" rel="noreferrer" target="_blank">https://bugreports.qt.io/browse/QTBUG-74492</a><br>
> will land soon at pypi, I've got some opengl tools in place where this<br>
> glitch makes really annoying work with them, it's a really disturbing bug :/<br>
<br>
As you can see in the bug report, the fix lands in Qt 5.12.5, 5.13.1 and 5.14.0.<br>
Via the Qt wiki, you can see when those are planned to be released:<br>
<br>
<a href="https://wiki.qt.io/Qt_5.12_Release" rel="noreferrer" target="_blank">https://wiki.qt.io/Qt_5.12_Release</a> (5.12.5: 27.08.2019)<br>
<a href="https://wiki.qt.io/Qt_5.13_Release" rel="noreferrer" target="_blank">https://wiki.qt.io/Qt_5.13_Release</a> (5.13.1: 15.08.2019)<br>
<a href="https://wiki.qt.io/Qt_5.14_Release" rel="noreferrer" target="_blank">https://wiki.qt.io/Qt_5.14_Release</a> (5.14.0: 26.11.2019)<br>
<br>
After a new Qt is released, usually a couple of days afterwards, PyQt gets<br>
updated (might be a bit longer for new feature releases like 5.14 will be).<br>
So if you're okay with upgrading to Qt 5.13, you'll hopefully see an updated<br>
PyQt in a month or so.<br>
<br>
I'd also recommend subscribing to the Qt Releasing mailinglist - it's quite<br>
low-traffic, and you get announcement mails when Qt updates are released, or<br>
when there was a release team meeting (with the meeting minutes):<br>
<br>
<a href="https://lists.qt-project.org/listinfo/releasing" rel="noreferrer" target="_blank">https://lists.qt-project.org/listinfo/releasing</a><br>
<br>
Florian<br>
<br>
-- <br>
<a href="https://www.qutebrowser.org" rel="noreferrer" target="_blank">https://www.qutebrowser.org</a> | <a href="mailto:me@the-compiler.org" target="_blank">me@the-compiler.org</a> (Mail/XMPP)<br>
GPG: 916E B0C8 FD55 A072 | <a href="https://the-compiler.org/pubkey.asc" rel="noreferrer" target="_blank">https://the-compiler.org/pubkey.asc</a><br>
I love long mails! | <a href="https://email.is-not-s.ms/" rel="noreferrer" target="_blank">https://email.is-not-s.ms/</a><br>
</blockquote></div>