The C-runtime library for Python 3 does NOT need a windows manifest
any longer to load correctly (this is a feature of Python, not of
py2exe).

py2exe now contains a hooks module which contains information about
some standard packages. The goal is to fine-tune the build process so
that no (at least less) warnings are emitted from modulefinder.

Thanks to a brand new modulefinder (based on Python’s importlib)
py2exe can now find and extract modules even from packages you have
installed as zipped eggs.

py2exe now longer uses a build directory for temporary files.

It is planned to achive full compatibility with the setup-scripts for
Python 2; however this is probably not yet the case.

In addition to your beloved setup.py scripts :-), there is now also a
command-line utility which allows to build the exe without any effort.

Running

py -3.4 -m py2exe.build_exe myscript.py

or (if you have the Python Scripts directory on your PATH):

build_exe myscript.py

will create an executable myscript.exe in the dist subdirectory.

If you add the -W<setup-script.py> switch to the above command
line a commentedsetup.py script will be generated which can be
used to further customize the exe:

Creating an executable (or more than one at the same time) with a
setup-script works in the same way as for Python 2. The command-line
switches are the same as before; but they are NOT compatible with
the command-line switches for the builder mentioned above.

Documentation about the setup-script and other usage tips are in the
wiki pages at http://www.py2exe.org.

The zip-archive is appended to the test_sqlite.exe file itself, which
has a size of 1.5 MB in this case.

--bundle-files 2 will include all the Python extensions into the
appended zip-archive; they are loaded via special code at runtime
without being unpacked to the file-system. The files in the
dist directory now are these:

test_sqlite.exe
python34.dll
sqlite3.dll

--bundle-files 1 will additionally pack the python-dll into the
zip-archive:

If you are building several related executables that you plan to
distribute together, it may make sense to specify a zip-archive shared
by all the exes with the --library libname option. The
executables will then become quite small (about 25 kB), since nearly
all code will be in the separate shared archive.

Note that not all applications will work with ``bundle-files`` set to
0 or 1. Be sure to test them.