27 April 2020
Cristián 🥑text not yet in the index
But, what if qt wheels for pyside2 and qt wheels for my lib will are different? For example, pyside2 wheels were built with CLang, my wheels with gcc 8,3. Sorry, I still not understand (
Just imagine the simple sitaution.
1. I added my pip package with my qt wheels compiled, for example, with gcc 8.3.
2. The pyside2 contains Qt wheels that compiled with clang.
3. The user import pyside2 and my package in the target python script.
4. The user will connect to the signals defined in my package via pyside2 QObject.connect
Are there any problems?
Ссылка
click to show
click to show
is that you should use only what's provided by the Itanium ABI http://itanium-cxx-abi.github.io/cxx-abi/
Cristián 🥑for that, you can just download a wheel for each platform, unzip it, and see which one are linked
Where can I download pyside2 wheels?
Cristián 🥑wheel, if you are planning to create wheels for your project, I'd expect you know where to find them :P
Ok, thank you! The wheels are required, I already understood it )
30 April 2020
Hello, I’ve decided to test the app under Python 3.6 using pyenv and get the strange behavior. I have a Signal defined in a top-level QML widget like this
ApplicationWindow {
…
signal backendLoaded(bool success)
onBackendLoaded: { … }
and emit it from the Python like this
main_window = engine.rootObjects()[0]
main_window.backendLoaded.emit(success) # inform the GUI
All works great on 3.7 and 3.8 but on 3.6.10 I got this