Since (unlike C++) you can put pretty much any Python expression into Expressions, you might get it with something like label.text().encode('utf-8'), or label.text().decode('utf-8') if it's decoding rather than encoding, don't ask me about encodings!). In both PyQt and PySide all QStrings are translated into Python strs, which are those 16-bit encoding thingies.

label.text().decode('utf-8') results in <unavailable>.

🤷🏻‍♂️

I didn't notice you were printing a duck/swan thing, wth is that? :)

🐍 https://emojipedia.org/snake

Since (unlike C++) you can put pretty much any Python expression into Expressions, you might get it with something like label.text().encode('utf-8'), or label.text().decode('utf-8') if it's decoding rather than encoding, don't ask me about encodings!). In both PyQt and PySide all QStrings are translated into Python strs, which are those 16-bit encoding thingies.

Just while we are here, I would give a limb if gdb/C++ Creator debugging would allow expressions to be evaluated in the Expressions pane. I understand the issue with C++ versus Python for expression evaluation, but it's the single most irritating thing when debugging C++.... :(

@cristian-adam
Alternatively as a workaround and still using the debugger panes rather than putting in a qDebug() statement, did you try putting label.text() into the bottom right Expressions pane?

Worked. I didn't give me Hello 🐍 but Hello =\d but I guess that's due to the missing UTF-8 encoding.

I've opened up QTCREATORBUG-34195: Python debugging not having pretty printers for Pyside6 Qt types.

And as workaround for the missing debugger, is the qDebug() trace:

from PySide6.QtCore import Qt, qDebug

# ...

    qDebug("Label text: " + label.text())

It did mention that on is a bool, was that it?

That is indeed the chappie :) It also shows the function call returns None, which is a type hint too.

Python decided not to have types initially. Then someone came to their senses and said "well we don't want mandatory types, but if you are finicky enough to want to type in types as hints we will let you do that". And then presumably someone said "these are really useful when editing, so we'll introduce warnings when they're wrong and editors can show them if they help people". :)

@cristian-adam
It looks like your latest post crossed with mine! That again is an improvement to show the parameters, good. But still no type hint (the type expected for the on parameter), is that supported? :) And I don't know whether all the Qt calls are annotated in the PySide with their types, that may require a manual step?

It did mention that on is a bool, was that it?

Equivalent to jumping to a header file in C++.

The code completion looks different now.

In oder to achieve this I've:

1. Went to Preferences > Python where I clicked on Python 3.13.12 then on the right the buttons: Make Default and then Generate Kit.

2. New Project and then in Application (Qt for Python) selected Empty Application

3. Pasted the content provided by gpt-oss with the prompt create a pyside6 application that has a window with a label "Hello 🐍" with a text size 18.

After step 2 I've been asked by Qt Creator if I want to install Pyside6 and clicked yes, and it did its magic.

I have little knowledge about Python, but it seems like code completion works.

Here are the Python LSP settings:

The debugging helpers are not that ... helpful:

UPDATE: For anybody reading this. Per @cristian-adam's posts and pictures below, the reddit posts from only two years ago and my own experience with trying to use Creator with Python several years back notwithstanding, it does appear that Creator has done a lot more work integrating with PySide/Python than in my time! So it would only be fair to give Creator/Python a go now without necessarily moving to PyCharm.