[cx-freeze-users] cx_Freeze 3.0.1

[Anthony T. <an...@co...>]

What is cx_Freeze?

cx_Freeze is a set of utilities for freezing Python scripts into
executables using many of the techniques found in Thomas Heller's
py2exe, Gordon McMillan's Installer and the Freeze utility that ships
with Python itself.


Where do I get it?

http://starship.python.net/crew/atuining
http://www.computronix.com/utilities.shtml
(it may be a few days before the second site is updated)


What's new?
  1) Added option --default-path which is used to specify the path used
     when finding modules. This is particularly useful when performing
     cross compilations (such as for building a frozen executable for
     Windows CE).
  2) Added option --shared-lib-name which can be used to specify the name
     of the shared library (DLL) implementing the Python runtime that is
     required for the frozen executable to work. This option is also
     particularly useful when cross compiling since the normal method for
     determining this information cannot be used.
  3) Added option --zip-include which allows for additional files to be
     added to the zip file that contains the modules that implement the
     Python script. Thanks to Barray Warsaw for providing the initial
     patch.
  4) Added support for handling read-only files properly. Thanks to Peter
     Grayson for pointing out the problem and providing a solution.
  5) Added support for a frozen executable to be a symbolic link. Thanks
     to Robert Kiendl for providing the initial patch.
  6) Enhanced the support for running a frozen executable that uses an
     existing Python installation to locate modules it requires. This is
     primarily of use for embedding Python where the interface is C but
     the ability to run from source is still desired.
  7) Modified the documentation to indicate that building from source on
     Windows currently requires the mingw compiler
     (http://www.mingw.org).
  8) Workaround the problem in Python 2.3 (fixed in Python 2.4) which
     causes a broken module to be left in sys.modules if an ImportError
     takes place during the execution of the code in that module. Thanks
     to Roger Binns for pointing this out.

-- 
Anthony Tuininga
an...@co...

Computronix
Distinctive Software. Real People.
Suite 200, 10216 - 124 Street NW
Edmonton, AB, Canada  T5N 4A3
Phone:	(780) 454-3700
Fax:	(780) 454-3838
http://www.computronix.com