[python-win32] Producing EXEs from Python Code

[Schollnick, Benjamin]

> |users.  Python is not installed on machines as they come, 
> nor would it be
> |likely that IT would take it upon themselves to keep workstations
> up-to-date
> |with the latest modules and libraries (e.g. BioPython) that 
> I need to use.
> |Py2exe is invaluable to me in distributing the code that I write and
> making it
> |usable amongst the less computer-literate in the institute.
> 
> Py2exe does that task admirably.  Do any of your "small utilities and
> scripts" contain GUI interfaces and/or connections to 
> database backends
> that require pre-installed client services and/or logins to 
> pre-existing
> accounts?

I alternatively use the McMillian Installer package instead.....
But Py2Exe & Installer are roughly comparable....

The main feature in both packages is the ability to effectively
roll the Python core into the exe, so that Python does not have to be
installed on the client system.

These packages will not prevent you from have to have ODBC connection,
logins
or other local machine configuration issues that would have to be handled
by hand normally.

Although, you could use the Win32 libraries, and create new drive mappings,
create desktop icons, and other Windows based issues in a local python
script that you have EXE'd...  (i.e. a Install runtime script)

Both Py2exe and Installer allow GUI creation...

In the case of the Installer package, it will go through, and examine
the code to see what is imported, and bundle that with the application.
(i.e. Tkinter, etc...)

			- Benjamin