Lines Matching +full:ship +full:- +full:to
8 ---------------
10 Freeze make it possible to ship arbitrary Python programs to people
18 the Python run-time. Some measures have been taken to avoid linking
22 written in Python that it uses) is not included in the binary --
23 instead, the compiled byte-code (the instruction stream used
25 protection of your Python source code, though not much -- a
26 disassembler for Python byte-code is available in the standard Python
31 How does Freeze know which modules to include?
32 ----------------------------------------------
34 Previous versions of Freeze used a pretty simple-minded algorithm to
36 lines starting with the word "import". It was pretty easy to trick it
40 This has been remedied: Freeze now uses the regular Python parser to
42 code for IMPORT instructions. It may still be confused -- it will not
43 know about calls to the __import__ built-in function, or about import
49 import mechanism, and uses exactly the same rules to find imported
52 to determine which modules are to be imported, while Freeze will do a
56 environment you're using to run Freeze is the same one that would be
57 used to run your program, which should also be the same whose sources
62 to run.)
66 --------------------
68 Normally, you should be able to use it as follows:
78 ------------------
82 M_<module>.c. To produce the frozen version of your program, you can
84 filename argument to Freeze was "hello.py", the binary will be called
87 Note: you can use the -o option to freeze to specify an alternative
88 directory where these files are created. This makes it easier to
94 -------------------------
96 Unfortunately, it is currently not possible to freeze programs that
97 use Tkinter without a Tcl/Tk installation. The best way to ship a
98 frozen Tkinter program is to decide in advance where you are going
99 to place the Tcl and Tk library files in the distributed setup, and
103 For example, assume you will ship your frozen program in the directory
104 <root>/bin/windows-x86 and will place your Tcl library files
115 sys.path = ['', '..\\..\\lib\\python-2.0']
120 sys.path = ['', '../../lib/python-2.0']
125 sys.path = ['', '../../lib/python-2.0']
130 This also adds <root>/lib/python-2.0 to your Python path
141 compile time - see the LIB_RUNTIME_DIR variable in the Tcl makefile.
146 A workaround to installing your Tcl library files with your frozen
149 to a temporary location when the program runs; this is currently left
150 as an exercise for the reader. An easier approach is to freeze the
152 or the Tix Stand-Alone-Module code. Of course, you can also simply
157 Under Windows if you use the -s windows option, writing
158 to stdout or stderr is an error.
159 The Tcl [info nameofexecutable] will be set to where the
165 --------------------------------------
170 work when you ship it to a site without a Python installation.
177 When this occurs, the best thing to do is usually to rebuild Python
179 section to declare a library path using sys.path, and place the modules
184 ---------------
187 best to start playing with a really simple program first (like the file
188 hello.py). If you can't get that to work there's something
189 fundamentally wrong -- perhaps you haven't installed Python. To do a
195 ----------------------------
197 Under Windows 95 or NT, you *must* use the -p option and point it to
200 WARNING: the resulting executable is not self-contained; it requires
208 command line C compiler (CL). To compile, run "nmake"; this will
213 In order for this to work, you must have built Python using the VC++
216 tree, and this is where the generated Makefile expects it to be. If
222 It is possible to create frozen programs that don't have a console
223 window, by specifying the option '-s windows'. See the Usage below.
226 -----
233 -p prefix: This is the prefix used when you ran ``make install''
236 The default is whatever sys.prefix evaluates to.
238 tree; then -P must point to the build tree.
240 -P exec_prefix: Like -p but this is the 'exec_prefix', used to
242 evaluates to, or the -p argument if given.
243 If -p points to the Python source tree, -P must point
244 to the build tree, if different.
246 -e extension: A directory containing additional .o files that
247 may be used to resolve modules. This directory
251 More than one -e option may be given.
253 -o dir: Directory where the output files are created; default '.'.
255 -m: Additional arguments are module names instead of filenames.
257 -a package=dir: Additional directories to be added to the package's
258 __path__. Used to simulate directories added by the
260 More than one -a option may be given for each package.
262 -l file: Pass the file to the linker (windows only)
264 -d: Debugging mode for the module finder.
266 -q: Make the module finder totally quiet.
268 -h: Print this help message.
270 -x module Exclude the specified module.
272 -i filename: Include a file with additional command line options. Used
273 to prevent command lines growing beyond the capabilities of
275 are read and the -i option replaced with the parsed
276 params (note - quoting args in this file is NOT supported)
278 -s subsystem: Specify the subsystem (For Windows only.);
281 -w: Toggle Windows (NT or 95) behavior.
282 (For debugging only -- on a win32 platform, win32 behavior
287 script: The Python script to be executed by the resulting binary.
291 may be .py or .pyc files. If -m is specified, these are
296 --Guido van Rossum (home page: http://www.python.org/~guido/)