@@ -30,7 +30,7 @@ results in a chain of processes being created - the wrapper itself, the virtual
3030environment redirector, and finally the Python interpreter. Creating all these
3131processes isn't cheap, and particularly for a small command line utility, it
3232impacts application startup time noticeably. Furthermore, the entry point
33- wrapper is a standard executable with a zipfile attached - because of this, the
33+ wrapper is a standard executable with a ZIP file attached - because of this, the
3434application cannot be signed in advance by the developer, and this is often seen
3535as "suspicious" by virus scanners. If a scan is triggered, this can make the
3636application even slower to start, as well as running the risk of "false
@@ -65,12 +65,14 @@ You can, if you wish, dump all of those items into a single directory. However,
6565it is much easier to manage the application if you keep them separate.
6666Therefore, the recommended layout is::
6767
68- Application directory
69- MyAwesomePythonApp.exe
70- interp
71- (embedded Python interpreter)
72- lib
73- (Python code implementing the application)
68+ Application directory/
69+ ├── MyAwesomePythonApp.exe
70+ ├── interp/
71+ │ ├── (embedded Python interpreter)
72+ │ └── ...
73+ └── lib/
74+ ├── (Python code implementing the application)
75+ └── ...
7476
7577The remainder of this guide will assume this layout.
7678
@@ -157,7 +159,7 @@ resulting file will look like this::
157159 # Uncomment to run site.main() automatically
158160 #import site
159161
160- If you have put your application Python code somewhere else, this is the only
162+ If you have placed your application's Python code somewhere else, this is the only
161163thing you need to change. The file contains a list of directories (relative to
162164the interpreter directory) which will be added to Python's ``sys.path `` when
163165starting the interpreter.
0 commit comments