Qt for Python (PySide/Shiboken)

Oh nice! I also found the pyi_generator script: https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/shiboken6/shibokenmodule/files.dir/shibokensupport/signature/lib/pyi_generator.py

that's for the standalone tool we provide, in case people want to use it with other shiboken-generated proyectos

It seems that the pyi-type attribute of the modify-argument tag eats the argument default value. I've dug to sources/shiboken6/ApiExtractor/typesystemparser.cpp and the parseModifyArgument function there. However, when I comment the argumentModification.setPyiType(pyiType); line out and re-run python setup.py build --reuse-build --module-subset=Core, I keep seeing that the types are replaced as before. Is the CPP file a wrong place?

I am trying to understand a very specific concept, which I am currently going deep down the rabithole. If one would consider a QComboBox. And this QComboBox is connected via a QDataWidgetMapper. Under the hood there is likely some QItemDelegate that does the magic where the model can have a plain string, and the QComboBox would correctly select the right item. Where / when does this text to currentItemIndex happen? What is basically the slot that is connected? Bigger question: what should a widget implement so it would not require custom QItemDelegates in the code by the user?

Oh, it calls the system-wide shiboken6. Where does the call come from? It all comes down to the generate_pyi.py script. And I can't go deeper for some reason. There is another virtual environment. Let's check it out…

Ok, yeah. But here: https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/PySide6/support/generate_pyi.py#n39 you do: from PySide6.support.signature.lib.pyi_generator import generate_pyi I'd assume that I could look in there via https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/PySide6/support/signature/lib/pyi_generator.py But this does not exist. So I searched it and found it there^ Are there different versions of this file?

Where is “there”?

The massage Christian was replying to

I'm about to give up. I've pushed the changes being unable to test them. There are people more clever than me.

Remember to add reviewers, otherwise they will probably bee forgotten. You can add "pyside" as a reviewer. Is a group with all the core devs

Anton, if you want to know more about .pyi generation in PySide, I can give you every info. Maybe we should contact in private.

(I'm certain more people will benefit if you have that conversation here though, but that is only my opninon 👀)

better to talk it through and then put the condensed extract here.

Thanks a lot! By now, the only question that bothers me is that no changes in the code of shiboken6-generator are applied to the produced *.pyi files. I command python setup.py build --reuse-build --module-subset=Core, it compiles the changes files related to shiboken6-generator, but the files remain the same (although re-written). I'm about to leave the work earlier today. Tomorrow I'll PM you if I may.

@StSav012 Ok. Just for short: You can change the XML. That will generate different binaries when you compile (probably better with a full build), and the executable code will then be introspected by the pyi generator. See you tomorrow.

Would anyone have a hint if there is a possibility to resolve this already 10 year old issue? It basically boils down to that each time setText is applied on a QLineEdit the cursor moves to the end of the widget. The hints on multiple places is: store the cursor position. But the more practical question is, if this is part of a DataWidgetMapper, how could you do this in a non-hacking way, preferably from the model directly. https://stackoverflow.com/questions/15801259/qlineedit-cursor-moves-to-end-after-textchanged-or-commitdata

@skinkie but that is a Qt question. We are providing the Python wrapper as good as we can, but are not involved in Qt design problems. Maybe that's because of the Qt for Python name. PySide was less misleading.