Hey Cristián, On Fri, Oct 25, 2019 at 11:48:06AM +0000, Cristián Maureira-Fredes wrote: > From 3.6 there are many features we wanted to use, like: > * f-strings (and refactor our code base), > * asyncio stable API (we wanted to move forward and provide compatibility), > * Type annotation for function parameters, > * default utf-8 encoding on windows for file system paths (we had a > couple of issues) > * The ability to check if the GIL is being held (to help us solve > a couple of problems with GIL and event loop), > * among others,
I understand (especially for f-strings!) - I'm in a similar boat with my own project (qutebrowser[1]), but I didn't dare to drop support for 3.5 yet. But what I don't understand: How are you going to use e.g. f-strings if you need to keep support for 2.7? [1] https://www.qutebrowser.org/ > If it's so critical to you, > I think this could be postponed to the release of Qt6 too, > after all the final release 3.5.8 is scheduled for tomorrow, > and then it naturally will be unused. Not for me - qutebrowser currently still only supports PyQt5. If PySide2 support was introduced, from qutebrowser's view it'd be fine to only support that on 3.6+. Other projects might feel different though. Florian -- https://www.qutebrowser.org | m...@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
_______________________________________________ PySide mailing list PySide@qt-project.org https://lists.qt-project.org/listinfo/pyside
