30 July 2026
id 24766519Yeah, that would be nice. But aren't they still on Qt 5.6?
Ссылка
click to show
click to show
Yes, the stable version is still Qt 5. I heard some unofficial version of Qt 6 support. But not released for end users. https://github.com/sailfishos-chum/qt6
I admire your enthusiasm, but it's very difficult to me to grasp these kind of response.
For many years, there was no support at all for mobile, and after a lot of work, the team managed to publish Android support. Do you know what the first message was? "What about iOS?"...fair enough, then more years passed, and again the team managed to finally have support for iOS, and what's the first message "I hope Sailfish OS supports PySide6".
Can we just enjoy what we have 😢? this really don't motivates people to keep providing support for new platforms, and instead of acknowledge that's not just "pip install magical-ios-support" and it was a lot of time of research, even an external collaborator managed to get around this, meetings, fixes in Qt, etc, etc ...
Hi Christian, I'm sorry that this is how it came across. I am extremely grateful for PySide6. It's not just super powerful but it *IS* actually just pip install PySide6 on all platforms I use it.
Maybe some background: Jolla released a new phone and started shipping it in the past days. Their entire stack is Qt-based but they officially only support 5.6. I was planning to tinker around and maybe develop an app but when I read their developer documentation I was like: I wish it was like PySide6 😅
So, I love your and your teams work, I really do think it's amazing!
Cristián 🥑I admire your enthusiasm, but it's very difficult to me to grasp these kind of response.
For many years, there was no support at all for mobile, and after a lot of work, the team managed to publish Android support. Do you know what the first message was? "What about iOS?"...fair enough, then more ye
I've been working in information tech for 27 years, and it's always this way. You implement X and immediately someone is asking about Y. Like can't we be happy for at least 5 minutes?
Cristián 🥑I admire your enthusiasm, but it's very difficult to me to grasp these kind of response.
For many years, there was no support at all for mobile, and after a lot of work, the team managed to publish Android support. Do you know what the first message was? "What about iOS?"...fair enough, then more ye
I do thumb up 👍 your post before the following message. I think it is kind of response too. Sorry for making you feeling bad.
Anupam BasakHey everyone, I am working on a PySide project and need to decide on what to use for documentation. What tooling would you recommend for documenting a pyside project?
For my the project for my PhD defence I went with the now semi-defunct mkdocs
Have a look at Zensical for the new version of it, I actually had a great experience
Lorenzo CastellinoFor my the project for my PhD defence I went with the now semi-defunct mkdocs
Have a look at Zensical for the new version of it, I actually had a great experience
Currently I am also using properdocs(the mkdocs successor with 100% compatibility with mkdocs plugins) along with the mkdocstrings-python handler to parse and build the documentation. But I am looking for alternatives that I could replace properdocs with.
I am using Google style docstring. I suppose it should be an easy enough migration to sphinx from properdocs.
The main problem I am facing with properdocs is its lack of awareness for Qt. Needs a bit of customisation for it to be able to parse the properties/signals/etc to get rendered correctly.
31 July 2026
I'm getting ImportError: cannot import name 'QModelRoleDataSpan' from 'PySide6.QtCore' when running under PySide 6.7. According to the C++ documentation, QModelRoleDataSpan should be available since Qt 6.0. But it somehow isn't there? Since the documentation for 6.7 was pruned, I can't verify if it was missing from older PySide. Do I need to increase the minimum version required to 6.8?
id 24766519I just checked and it should be available on 6.8.x
Thanks. That's what my test suite told me, too. So for now, I've bumped the minimum required version to 6.8.
For major dependencies, my tox configuration generates an environment for each major (minor) version I claim support with. The linear sweep across PySide6 revealed that 6.7 no longer works after i implemented multiData(), which takes a QModelRoleDataSpan as an argument.
4 August 2026
PySide Bot(irc) uuuuu: a = QStackedLayout() a.setStackingMode(QStackedLayout.StackingMode.StackAll) doesn't seem to be working. Items under label can't be seen and setting index will just show one widget at a time
Afaik widgets have opaque backgrounds, so the top widget backgrounds paints over the entire drawing area
PySide Bot(irc) uuuuu: how would I set the position of a qlabel on a qstackedlayout. Is there a way to do it using stylesheet?
The stacked layout takes QWidgets.
So... I'd set a QGridLayout (or a QWidget with such a layout set), and place the QLabel in there. Then use the row and column spacing weights to position it relatively to the widget origin
PySide Bot(irc) uuuuu: would I be able to see multiple stacked widget with qgridlayout
Not sure. Probably, because it has no background. But you can customize the widget rendering and disable the background. Can't tell exactly from memory, but I know that's possible
PySide Bot(irc) uuuuu: and the pixmap will take up the whole space
Hmm. Will the background pixmap label need to handle any kind of input? Or is there more than two layers?
If not, there's a simpler solution than a stacked layout.