A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-list/2005-September/306054.html below:

Getting tired with py2exe

Getting tired with py2exeBugs dont at spam.me
Tue Sep 20 17:15:45 EDT 2005
Steve M wrote:
[snip]
>  * Dual packaging mode:
>    * Single directory: build a directory containing an executable plus
> all
> the external binary modules (.dll, .pyd, .so) used by the program.
>    * Single file: build a single executable file, totally
> self-contained,
> which runs without any external dependency.
[snip]

I've never used pyinstaller but even though it can create a single 
executable file, doesn't it still write files out to the filesystem to a 
  temp directory for actual execution?  Then cleans them up when the 
application quits?

Whereas py2exe can create an executable that NEVER writes any files out 
to the filesystem, they are loaded instead directly from the executable?

If so then that's a major difference and IMHO the py2exe method is superior.

More information about the Python-list mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4