error qtpy.PythonQtError: No Qt bindings could be found

Hello,

So i am attempting to setup a new image for my RPI4 64 bit

when i attempt to run any qtpyvcp interfaces i get an error
"qtpy.PythonQtError: No Qt bindings could be found"

I am using the image provided here
forum.linuxcnc.org/9-installing-linuxcnc...blem?start=90#217552

I also am using a dep package of VTK made with qt5 python2.7 and opengl
drive.google.com/file/d/1ocUkoVSPSBseyNy...aN0/view?usp=sharing

when i run "qtpyvcp -v" i get the following
QtPyVCP python3_master

Any idea on what step i have messed up?

so if i run qmake it shows i have qt5.

Is there another way to test to make sure the bindings are there?

I am at a loss for ideas.

My only option now is to clone my existing hdd but i wanted to be able to create a new image.

On the RPI front I can't help as not ever been down that rabbit hole.

I can let you know that pyqtvcp master is python 3 only.  So anything built for py2 will not work with it.  e.g. your py2 vtk.

This py2 v's py3 will also be relevant to any dependencies you have grabbed/installed and potentially what is seen as the default python on the RPI.  Things are MUCH simpler if your OS is py3 only and there is no py2 about to confuse the issues.  OR if there is py2 it has come in later and the OS considers py3 the master and as such is first in all search paths.

There is a py2 maintenance branch on qtpyvcp repo that might be worth doing or install the "offical" qtpyvcp installers that are py2 only.  But please note the only way to get any fixes to the py2 path is, at the moment, to clone and checkout the python2_maintenance branch.

Cheers - J.

this may be the problem.
Going to start with a fresh image and use the one you mentioned.
Thank god for the way back machine, i can see now that i  have been installing the wrong things as i just noticed they were definitely all for python 3.
So my first task it to get it working with python 2.7
Then i will spin up another drive and remake VTK with pthon3 and try the latest master.

you were 100% right it was me trying to use the python 3 version!

Ohh the feeling of finally getting this working.

and now that i look back i should have seen it. its even in my print out statement
"when i run "qtpyvcp -v" i get the following
QtPyVCP python3_master"

Its right there staring me in the face but i was just to dense to notice.

So happy it was a simple fix but at the same time feel so dumb.

But hey i have learned a few things
1, make my own VTK version
2. turn that into a deb package. (thanks scott for pointing me to checkinstall)
3. python 3 != python 2.7