Wrapping Python ?
USCode
uscode at dontspam.me
Sat Sep 25 15:02:20 EDT 2004
"Peter Hansen" <peter at engcorp.com> wrote in
>
> In what way is it not the same thing? (Hint: I'm not about to
> follow those links and learn about the products just to answer
> the question... maybe you could explain it, since you seem to
> be the one who knows about all three products.)
>
> Also could you explain in what way you feel py2exe is not as
> "comprehensive"? It does what it does, does it well, and
> doesn't really seem to be missing much in that area. Maybe
> you are looking for an "installer" as well, such as InnoSetup?
>
> -Peter
I think the key difference is that they support the concept of a virtual
file system within the executable whereas, if I understand correctly, the
executable created by py2exe writes attached modules to the local disk in
specific directories before executing.
With Freewrap, it uses the Zip Virtual File System so as the attached ZIP
archive can be opened so its contents look like a simple file subdirectory.
>From the Starkit website - "A Starkit creates the illusion of a "file system
in a file" - on the outside, it's a single file, yet the application code
continues to see a complete directory of scripts, extensions, packages,
images, and whatever other files it needs."
Also, another key difference is both the Tcl/Tk wrapping utilities are
cross-platform with both of them working on Windows and Linux. Starkit
works on OSX and lots of other platforms as well.
I'd like to generate a single executable without needing an installer or
files needing to be written out to the local disk before execution, etc.
Sorry if I'm wrong regarding the capabilities of py2exe. Otherwise perhaps
it could be enhanced someday to utilize a VFS as well.
Thanks!
More information about the Python-list
mailing list