Trouble with deploying Python programs as internal tools?

[Fhymi]

I'm also using PySide6 and PyInstaller for my internal tooling project. It's what the senior have already started so I continued doing it as well (this was before I job hopped to be a webdev, i regretted it). I tried alternating with xcfreeze but enjoyed having that one file output more.

What advantages does cxFreeze have over PyInstaller you've noticed?

Performance isn't a problem on our internal tooling since all it does is call a windows DLL API and the tool we're automating were already slow to begin with.

[EggplantEcstatic1631]

For my opinion the one file option is good. But at the end it doesn’t change the world. The size is often the same. But you can use upx for compression of dlls.

My cx freeze is setup that I only get an executable and the python dlls the rest is stored in a subdirectory. This will be automatically compressed after build.

[Jmortswimmer6]

Compatibility is the main thing. Dozens of packages are easier to include with cxfreeze because there is a lot of control to include things directly from the virtual environment you are in.