{ "info": { "author": "Thomas Heller", "author_email": "theller@ctypes.org", "bugtrack_url": null, "classifiers": [ "Development Status :: 4 - Beta", "Environment :: Console", "License :: OSI Approved :: MIT License", "License :: OSI Approved :: Mozilla Public License 2.0 (MPL 2.0)", "Operating System :: Microsoft :: Windows", "Programming Language :: C", "Programming Language :: Python :: 3", "Programming Language :: Python :: 3.3", "Programming Language :: Python :: 3.4", "Programming Language :: Python :: Implementation :: CPython", "Topic :: Software Development", "Topic :: Software Development :: Libraries", "Topic :: Software Development :: Libraries :: Python Modules", "Topic :: System :: Software Distribution", "Topic :: Utilities" ], "description": "py2exe for Python 3\n===================\n\n`py2exe` is a distutils extension which allows to build standalone\nWindows executable programs (32-bit and 64-bit) from Python scripts;\nPython 3.3 and later are supported. It can build console executables,\nwindows (GUI) executables, windows services, and DLL/EXE COM servers.\n\npy2exe for Python 2 is still available at\nhttp://sourceforge.net/project/showfiles.php?group_id=15583.\n\n.. contents::\n\nChanges\n-------\n\nVersion 0.9.2.2: Added support for six, cffi, pycparser, openssl.\nSupport cmdline_style (\"py2exe\", \"pywin32\", \"custom\") again for\nwindows services.\nSeveral bugfixes, better error messages.\n\n\nNews\n----\n\nThe C-runtime library for Python 3 does NOT need a windows manifest\nany longer to load correctly (this is a feature of Python, not of\npy2exe).\n\n`py2exe` now contains a hooks module which contains information about\nsome standard packages. The goal is to fine-tune the build process so\nthat no (at least less) warnings are emitted from modulefinder.\n\nThanks to a brand new modulefinder (based on Python's importlib)\npy2exe can now find and extract modules even from packages you have\ninstalled as zipped eggs.\n\npy2exe now longer uses a `build` directory for temporary files.\n\nIt is planned to achive full compatibility with the setup-scripts for\nPython 2; however this is probably not yet the case.\n\n\nIn addition to your beloved setup.py scripts :-), there is now also a\ncommand-line utility which allows to build the exe without any effort.\n\nRunning\n\n::\n\n py -3.4 -m py2exe.build_exe myscript.py\n\nor (if you have the Python ``Scripts`` directory on your PATH):\n\n::\n\n build_exe myscript.py\n\n\nwill create an executable `myscript.exe` in the `dist` subdirectory.\n\nIf you add the ``-W `` switch to the above command\nline a *commented* ``setup.py`` script will be generated which can be\nused to further customize the exe:\n\n::\n\n py -3.4 -m py2exe myscript.py -W mysetup.py\n ... edit myssetup.py\n py -3.4 mysetup.py py2exe\n\n\nInstallation\n------------\n\n::\n\n py -3.4 -m pip install py2exe\n\nor\n\n::\n\n pip install py2exe\n\n\nUsing the builder\n-----------------\n\nBuild runtime archive for a script:\n\n::\n\n build_exe [-h] [-i modname] [-x modname] [-p package_name] [-O] [-s]\n [-r] [-f modname] [-v] [-c] [-d DESTDIR] [-l LIBNAME]\n [-b {0,1,2,3}] [-W setup_path]\n\t\t [-svc service]\n [script [script ...]]\n\n\npositional arguments:\n script\n\noptional arguments:\n -h, --help show this help message and exit\n -i modname, --include modname\n module to include\n -x modname, --exclude modname\n module to exclude\n -p package_name, --package package_name\n module to exclude\n -O, --optimize use optimized bytecode\n -s, --summary print a single line listing how many modules were\n found and how many modules are missing\n -r, --report print a detailed report listing all found modules, the\n missing modules, and which module imported them.\n -f modname, --from modname\n print where the module is imported.\n -v verbose output\n -c, --compress create a compressed library\n -d DESTDIR, --dest DESTDIR\n destination directory\n -l LIBNAME, --library LIBNAME\n relative pathname of the python archive\n\n -b option, --bundle-files option\n How to bundle the files:\n 3 - create script.exe, python.dll, extensions.pyd, others.dll.\n 2 - create script.exe, python.dll, others.dll.\n 1 - create script.exe, others.dll.\n 0 - create script.exe.\n\n -W setup_path, --write-setup-script setup_path\n Do not build the executables; instead write a setup\n script that allows further customizations of the build\n process.\n\n -svc svnmodule, --service svcmodule\n The name of a module that contains a service\n\nUsing a setup-script\n--------------------\n\nCreating an executable (or more than one at the same time) with a\nsetup-script works in the same way as for Python 2. The command-line\nswitches are the same as before; but they are *NOT* compatible with\nthe command-line switches for the builder mentioned above.\n\nDocumentation about the setup-script and other usage tips are in the\nwiki pages at http://www.py2exe.org.\n\n\nThe bundle-files option explained\n---------------------------------\n\nThe applications that py2exe creates will always need the following\nparts:\n\n1. The exe-file(s) itself. py2exe can build several executables at the\n same time; this is especially useful if these are related to each\n other since some parts can be shared.\n2. The python-dll.\n3. The pure python modules needed to run the app. The byte-code for these\n modules is always packed into a zip-archive.\n4. Compiled python-extension modules.\n5. Supporting dlls, if any.\n\nThe bundle-files option determines how these files are packed together\nfor your application. This is explained with a script ``test_sqlite.py``\nthat simply contains this code:\n\n::\n\n import sqlite3\n print(sqlite3)\n\nThe command to build the exe-file is:\n\n::\n\n py2exe.build_exe test_sqlite.py -c --bundle-files