PyInstaller VS py2exe

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

See this GitHub issue to follow the relevant discussion and development.

There are ways to bundle Python with your application using something like py2exe

Then you can turn the python program to an actual executable, a normal .exe file that user just launches and uses. If you chose to use this way, look into PyInstaller or py2exe. The executables will be obviously bigger, I think at least PyInstaller pretty much just packages Python and your script into .exe to make it work, so every program would be quite big (as each program has its own Python packaged). I also heard the process of turning the scripts to .exe is sometimes a bit problematic if you use some fancy imports and you also might run into problems with architecture.

*fyi, you can use a tool like py2exe or PyInstaller to convert Python scripts into a Windows Executable.

py2exe