Getting stuck at yt_dlp.extractor.lazy_extrac about nuitka HOT 4 OPEN

You might want to use no --include-package and instead report the missing dependencies so they can be fixed, and at least use only --include-module as it otherwise includes a lot of code, and you probably run out of memory.

from nuitka.

It remains stuck at that point with no increase in ram or CPU usage.
when i run with just

python3 -m nuitka main.py

It creates a .bin file which I can execute from my application path which contains other folders like images, configs, libraries, models etc.

Ill try adding those missing dependency folders one by one to the path.

But I want to create a single executable which will run the app standalone. If i run with just python3 -m nuitka --follow-imports main.py the follow imports also gets stuck at that point where yt-dlib gets stuck at extract. How should i proceed if i want to add the python and other dependencies also into the standalone folder package?

from nuitka.

Thank you for your help!
When I simply run

python3 -m nuitka main.py

It creates a main.bin file, and if i run that file from my folder everything in that PyQT5 application works perfectly. I had read there were issues with callback and threading in your pyqt5 support doc, but even threading using background processes and event callbacks are working properly.

I am only facing 1 major issue with the camera stream callback which happens through a slot signal mechanis,, where an image is updated from the background stream. The process runs in the background as per the logs but the image, does'nt seem to render, but if the process is killed, a single image is rendered after the event end.

Other threaded screen updates using signals and slots and events are working properly. Seems like this one issue could also be workedaround which would save an entire migration to pyqt6 due to many dependencies to be handled.

The doc had suggested very limiting workarounds, do you think If i try, this single threaded signal for images could also be fixed through a workaround? You have better understanding as to guide if I should put my effort in this or look for another solution.

from nuitka.

How about you report the output of --standalone --noinclude-custom-mode=yt_dlp:error and we remove as bloat, if that's unused. For distribution compiling the top level file only won't do much.

from nuitka.