PyInstaller VS pyinstxtractor

Not sure if fixed in this patch, but pyinstaller had an issue in 3.12.0 https://github.com/pyinstaller/pyinstaller/issues/7992

You are right. I think I've misremembered the module name - it was uwsgi, not uvicorn.

This is a github issue where I discussed my original issue with PyInstaller devs - the dev explained the situation very well: https://github.com/pyinstaller/pyinstaller/issues/6362

PyInstaller seemed like the most maintained and developed tool to freeze python script into an executable, so I went with it. As expected, the freezed interface with the model was gigabytes large, so I had to figure out how to squeeze this. Fortunately, Onnx worked wonders and packaged the model into an inference only state, so I could throw away the Pytorch and Torchtext dependencies when freezing with Pyinstaller.Now the size of the executable with the model was 43MB instead of 4GB.

You might want to see Pyinstaller and auto_py_to_exe if you want a GUI interface.

It uses the pyinstaller command behind and please read their docs if you want to know more details.

I also found another link on github that may have some solutions to try: https://github.com/pyinstaller/pyinstaller/issues/3600

I made a Django react app. Now I want to make it a desktop application so that the user does not have type python manage.py runserver and also activate the environment every time. I used pyinstaller. I did all the steps mentioned for django

First, instead of creating a VM for windows, you may need to use a software called Wine mentioned in the pyinstaller FAQs

I have used pyinstxtractor to extract the *.pyc files, and then the uncomplyle6 to decompile the *.pyc files. Which has led me to the actual source code of the binary:

Also, be real, you mention you use it once in the credits at the bottom of your readme while also advertising your mate's tool that ALSO looks like it uses identical code to the original, this time without even mentioning it. And given he also makes CS:GO cheat tools by the looks of it, I struggle to understand why any of you think you have the moral high ground in any of this...

It's a Pyinstaller binary.(I have used it once before, so I just knew it by checking the file.) Use https://github.com/extremecoders-re/pyinstxtractor to extract its source code archive in binary (by just running python pyinstxtractor.py ./backdoor or something), now many .pyc files are extracted. Find src.pyc and it's malformed as Python3.9, so https://github.com/rocky/python-uncompyle6/ denies to decompile. But challenge information says it's Python3.8, so I write helloworld python script and execute it with Python3.8. It yields Python3.8 .pyc file. Analyze it and find signature is \x55. Change src.pyc's signature from \x61 to \x55 and decompile by running uncompyle6 backdoor-src.38.pyc > backdoor-src.py

If it's a pyinstaller blob, you can crack it open with tools like https://github.com/extremecoders-re/pyinstxtractor

auto-py-to-exe is a GUI interface for PyInstaller (a famous freezer packager for python projects). While very user friendly, it should be noted that the .exe made using PyInstaller (or auto-py-to-exe) is very easy to reverse engineer (https://github.com/extremecoders-re/pyinstxtractor).

which boils down to slapping the Python Interpreter + the code in an executable form it is trivially easy to access the code inside such executables: https://github.com/extremecoders-re/pyinstxtractor