PyInstaller
PyInstaller and UPX on Linux - No change in file size with or without UPX #6275
|
I am trying to use PyInstaller and UPX to bundle a flask application on Ubuntu. When I run: pyinstaller app.py --onefile --cleanthe logs show that UPX is available: 297 INFO: UPX is available.However, in the entire log file, there doesn't seem to be a single instance of PyInstaller calling UPX. Consequently, the file size remains same irrespective of whether UPX is installed or not. I did not face this issue on Windows with the same command as above. The docs say:
Clearly I don't need to specify |
Replies: 1 comment 9 replies
|
You're right, UPX is actually used only on Windows. See #5966. |
Not by us - we have enough other issues to keep us busy... FWIW, since #7707, you can force-enable UPX by setting Contemporary versions of UPX on bleeding-edge linux distributions (I have 5.0.2 on my Fedora 42 system) seem to raise |
|
UPX on Arch (also 5.0.2) seems to work well for me now. Building I guess if we can make UPX opt-in rather than opt-out (#8653) then we no longer need to gatekeep who can run UPX safely. |
Seems to also work for Debian Bookworm. I guess
True. (Although the primary motivation there is to ensure it is opt-in on Windows). But now I'm starting to think that we should probably also make it explicit opt-in for existing spec files - for example by renaming the |
No worries, I was mainly wondering if I had missed something before trying out this super simple reproducer https://github.com/orgs/pyinstaller/discussions/8922#discussioncomment-11571639 and opening an issue myself. Although I also just read https://github.com/orgs/pyinstaller/discussions/8922#discussioncomment-13185670 , and as bwoodsend just mentioned, a simple hello world reproducer no longer triggers a segfault with latest UPX.
My use-case is debian-based anyway (if someone wants to use my Python project on Arch or Fedora, they're welcome to figure out the package installation, build, and IO permissions themselves...)
Interesting, I might play around with it later. Reading that other discussion topic about UPX 5.0.1, I'm not expecting much given I'm using PySide (Qt) and Slightly off-topic, but still relevant when raising segmentation fault issues to UPX: upx/upx#911 (comment)
|
|
I've had to exclude a few directories (I didn't bother finding exactly which libraries were causing segmentation faults), but got a claimed 53% compression on 22 files. Resulting in a total reduction of $soFilesToCompress = Get-ChildItem -Path ./dist/AutoSplit -Recurse -File -Filter '*.so*' |
Where-Object {
-not (
# _internal/*.so* causes Segmentation fault
$_.Directory -like '*/AutoSplit/_internal' -or
# _internal/PySide6/Qt/*/*.so* causes Segmentation fault
# _internal/PySide6/Qt/plugins/*/*.so* breaks style
$_.Directory -like '*/AutoSplit/_internal/PySide6/Qt/*'
)
}
./scripts/.upx/upx --lzma --best ./dist/AutoSplit/AutoSplit $soFilesToCompressResults: Oh and for fun, here's the results with and w/o upx+strip: |
You're right, UPX is actually used only on Windows. See #5966.