ChatCrawlersearch across public Telegram Open the app
Q

Qt for Python (PySide/Shiboken)

10 August 2022
2022-08-10×
10 August 2022
Cristián 🥑
lpapp: did you try removing the offending lines? the main problem is that your local Qt does not have those QCbor* signatures for some reason, so shiboken is complaining you have them on your typesystem. In case you do have those signatures, and they are not being detected, you'd need to report a specific bug on that, but I do recall that that was a Qt/C++ issue at some point. Did you check if the functions exist in your local Qt? lpapp: if you have any '_Check' function alone, there is something wrong with your typesystem, because that usually generate Type_Check functions based on the signature of your modules. I'd recommend you to look on the current typesystem files, and find a similar function that might behave as the ones you are trying to expose.
by 'current' I mean the pyside project ones. It might be the case that what you are trying to do is done there, so you can find pointers on how to proceed
std::string doesn't need anything else besides declaring it as a primitive-type in 5.15
it seems you are mixing things a bit
you expose classes and methods from C++ to Python
no statements, so having std::string res = "foo" doesn't apply to binding generation.
you will have methods that take std::string as an argument, others than return one, etc. But not a statement
both add-function and inject-code needs a transformation from Python types, to your internals
then you don't deal with "std::string" you deal with PyUnicode
if then maybe your question, how do I transform a Python string into a std::string ?
then the converttopython apply, but you don't need to return c++ types, you return Python types.
you can check the sources/pyside2/PySide2/glue directory for all the snippets currently used in the project, you might find what you are looking there
At least for me it was easier to start with the shiboken examples, to learn how they work. First 'samplebinding', then 'widgetbinding' then 'scriptableapplication' https://code.qt.io/cgit/pyside/pyside-setup.git/tree/examples After that I checked the current implementation of typical classes in Qt, like QByteArray, QVector, QPushButton and how the typesystem was defined for those https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside6/PySide6, and lastly I refer to the shiboken docs https://doc.qt.io/qtforpython/shiboken6/index.html
The whole 5.15 story is affected by the lts license development. Iirc it should be out soon. You need to somewhat calculate the official release and add 11 months. That's why we recommend people to use 6.x, because 5.15 is in the .10 release soon but only for license holders
It's not kde only, it's the kde free qt foundation that has been in place for a long time. That effort includes many folks besides kde people.
There is Readme file next to those examples
That's the only documentation besides the videos that briefly mention some of the shiboken stuff
Both qt and pyside are released at the same time most of the time. If the Qt source is released on the download.qt.io page, pyside will as well, if not, it's mainly due to a human factor, meaning we just need to upload it :p
That's because the commercial lts branches are in a separate repo, as Qt does.
I know, but that doesn't imply that there is a tag on the oss repo. We just release the source code
Because, as i mentioned, the lts code from 5.15.3-4 is on a diferent repo
Because the code is moved to a separate repo. It doesn't exist on the oss ones.
Then you need to follow the discussions on the development mailing list. This decision was made long time ago
Qt for Python follows what the qt project decides
Then you should bring your concerns to the mailing list. Python projects are not distributed via Conan, so it's not a priority atm
I'm jumping into a plane now, hopefully you can find your answers by other folks here.
C
You can file a bug report in any case to follow the discussion there.
Keith Kyzivat
@lpapp I think you're right: $ git -C qtbase tag --list *lgpl v5.15.3-lts-lgpl v5.15.4-lts-lgpl v5.15.5-lts-lgpl $ git -C pyside-setup tag --list *lgpl I had noticed this a month or two ago, and have been meaning to report it. pyside-setup should follow same approach that the other qt repos are using. I don't think it's intentional, but rather just an oversight.
K
@lpapp , could you search bugreports.qt.io for if it has been reported already, and if not, report it as a bug?
Calendar: August 2022
MoTuWeThFrSaSu1223445406786941029111812131415161718191201212212322243251262732829193025313
Archive by month
September 2026August 2026July 2026June 2026May 2026April 2026March 2026February 2026January 2026December 2025November 2025October 2025September 2025August 2025July 2025June 2025May 2025April 2025March 2025February 2025January 2025December 2024November 2024October 2024September 2024August 2024July 2024June 2024May 2024April 2024March 2024February 2024January 2024December 2023November 2023October 2023September 2023August 2023July 2023June 2023May 2023April 2023March 2023February 2023January 2023December 2022November 2022October 2022September 2022August 2022July 2022June 2022May 2022April 2022March 2022February 2022January 2022December 2021November 2021October 2021September 2021August 2021July 2021June 2021May 2021April 2021March 2021February 2021January 2021December 2020November 2020October 2020September 2020August 2020July 2020June 2020May 2020April 2020March 2020February 2020January 2020December 2019
Open in Telegram Каталог площадок Искать в ChatCrawler

A snapshot of an open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog