Qt for Python (PySide/Shiboken) — public feed snapshot · snapshot for October 2022

27 October 2022

Cristián 🥑

https://testresults.qt.io/coin/?project=pyside%2Fpyside-setup

12:48

alexis jeandet

I see, I was more thinking about some docker env usable to build my C++ code wrapped with shiboken

12:51

Cristián 🥑

ah, sorry but no, we don't use docker

12:52

alexis jeandet

Do you know if there are any project building wheels for PyPi using shiboken generator? I searched on github and PyPi but most projects I found use PyQt and swig :/

12:55

I'm searching some working setups (libc/compiler/Qt SDK....) to produce valid binary wheels for PyPI

12:56

Cristián 🥑

alexis jeandetDo you know if there are any project building wheels for PyPi using shiboken generator? I searched on github and PyPi but most projects I found use PyQt and swig :/

I'd say the most popular binding generation tool out there is pybind11, swig was really painful to work with from my exp. shiboken was used for the python bindings of Qwt, but they didn't generate any wheel :( (I guess you mean "sip and swig", sip is the 'shiboken' of PyQt hehe)

13:11

alexis jeandet

Yeah I use Pybind11 a lot for other projects, here I want to basically wrap a plot API based on QCustomPlot.

13:14

We started this APP as a full C++ code using Qt and PyBind11 but then it is quite hard to extend the GUI from Python and since this is a scientific app we also wanted an integrated jupyter terminal.

13:16

So I switched to a Python app using mostly PySide with few strategic bits like plots written in C++.

13:17

id 1588193098

Cristián 🥑text not yet in the index

Sorry, I meant the files. I can see them in the Linux and macOS wheels, but not in the wheel package for Windows.

14:12

Cristián 🥑

might be a bug from the CI provisioning

14:15

feel free to comment on the original issue 👍 thanks for noticing