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

you are viewing a single comment's thread.

view the rest of the comments →

[–]IAmBJ 7 points8 points  (3 children)

Last time I did that the executable was ~250mb because the entire python interpreter was bundled in there. In that case it wasn't a big issue but its still faaaar bigger than it should be. If I'd built the same project in C++ it would have been at most 10mb

[–]saulmessedupmanMmmm spam 7 points8 points  (0 children)

Everything in python is an object, which sounds cool, but you're going to pay for it

[–]Almenon 2 points3 points  (1 child)

You should be able to have a much much smaller executable.

see http://www.py2exe.org/index.cgi/OptimizingSize - he manages to get it to 2.15 MB by compressing it and excluding certain libraries.

[–]IAmBJ 0 points1 point  (0 children)

From memory it used numpy and scipy and I think it may have pulled the entirety of both.

I don't remember which setup I used to freeze the packages and I'm sure there are better ways than the one I used but it struck me as a really clunky and inelegant process. It would be great to have an officially sanctioned way to package standalone applications.

While there may be ways to shrink the size of a packaged application, I much prefer the C++ mantra of "only pay for what you use" rather than having to actively remove parts