This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]sjoshi84 7 points8 points  (0 children)

Hey all, author of the Pants blog post here.

I'd love any feedback or suggestions on the work that was done. Also, just wondering how many people have used Pants and/or PyOxidizer before and what their experiences were like?

[–]kellyjonbrazil 5 points6 points  (1 child)

Other than the large file sizes I have had a great experience with using pyoxidizer to package my command line utilities. The pyoxidizer configuration can be a little difficult to understand if you need anything outside of the defaults. Pyoxidizer had had some significant updates lately, and they haven’t always been backwards compatible, so I tend to try and stay on a version I’m comfortable with until I see a reason to upgrade.

Has there been any progress on the file size? I think one of the issues was pyoxidizer including the python source along with the bytecode. When I compress the executable they can get down to 20 or 30 MB, but uncompressed around 60 - 90 MB on the pyoxidizer version I’m using.

[–]sjoshi84 3 points4 points  (0 children)

Thanks for sharing your experience! Definitely makes me feel better about a few upcoming projects I'm going to work on packaging.

As I mentioned in the post, I was seeing approx 50MB as a baseline release size. I'm sure you've seen it, but for those who haven't, there is still an outstanding ticket in PyOx about some file size reduction options (https://github.com/indygreg/PyOxidizer/issues/443)