Part 2: If you want to start as admin on logon without the UAC elevation prompt, use the Task Scheduler. The important options you need: 'Change User' to your own. Select 'Run only when user is logged on'. Check 'Run with highest privileges'. Uncheck everything on the Settings tab except maybe 'Allow task to be run on demand' (to allow you to. If you have an admin account on your machine (where you can install your own apps), click the gold lock on the bottom left side and authorize your access, then proceed to step 6. If you don't have an admin account, stop here and call SSI Support on 415-483-1700. Click on 'Camera' in the left part of the window.

The syntax of the pyinstaller command is:

pyinstaller [options] script [script …] | specfile

In the most simple case,set the current directory to the location of your program myscript.pyand execute:

PyInstaller analyzes myscript.py and:

Writes myscript.spec in the same folder as the script.
Creates a folder build in the same folder as the script if it does not exist.
Writes some log files and working files in the build folder.
Creates a folder dist in the same folder as the script if it does not exist.
Writes the myscript executable folder in the dist folder.

In the dist folder you find the bundled app you distribute to your users.

Normally you name one script on the command line.If you name more, all are analyzed and included in the output.However, the first script named supplies the name for thespec file and for the executable folder or file.Its code is the first to execute at run-time.

For certain uses you may edit the contents of myscript.spec(described under Using Spec Files).After you do this, you name the spec file to PyInstaller instead of the script:

pyinstallermyscript.spec

The myscript.spec file contains most of the informationprovided by the options that were specified whenpyinstaller (or pyi-makespec)was run with the script file as the argument.You typically do not need to specify any options when runningpyinstaller with the spec file.Only a few command-line optionshave an effect when building from a spec file.

You may give a path to the script or spec file, for example

or, on Windows,

pyinstaller'C:DocumentsandSettingsprojectmyscript.spec'

Options¶

General Options¶

`-h, --help`	show this help message and exit
`-v, --version`	Show program version info and exit.
`--distpath DIR`	Where to put the bundled app (default: ./dist)
`--workpath WORKPATH`
Where to put all the temporary work files, .log, .pyzand etc. (default: ./build)
`-y, --noconfirm`
Replace output directory (default:SPECPATH/dist/SPECNAME) without asking forconfirmation
`--upx-dir UPX_DIR`
Path to UPX utility (default: search the executionpath)
`-a, --ascii`	Do not include unicode encoding support (default:included if available)
`--clean`	Clean PyInstaller cache and remove temporary filesbefore building.
`--log-level LEVEL`
Amount of detail in build-time console messages. LEVELmay be one of TRACE, DEBUG, INFO, WARN, ERROR,CRITICAL (default: INFO).

What to generate¶

`-D, --onedir`	Create a one-folder bundle containing an executable(default)
`-F, --onefile`	Create a one-file bundled executable.
`--specpath DIR`	Folder to store the generated spec file (default:current directory)
`-n NAME, --name NAME`
Name to assign to the bundled app and spec file(default: first script’s basename)

What to bundle, where to search¶

`--add-data <SRC;DEST or SRC:DEST>`
Additional non-binary files or folders to be added tothe executable. The path separator is platformspecific, `os.pathsep` (which is `;` on Windowsand `:` on most unix systems) is used. This optioncan be used multiple times.
`--add-binary <SRC;DEST or SRC:DEST>`
Additional binary files to be added to the executable.See the `--add-data` option for more details. Thisoption can be used multiple times.
`-p DIR, --paths DIR`
A path to search for imports (like using PYTHONPATH).Multiple paths are allowed, separated by ‘:’, or usethis option multiple times
`--hidden-import MODULENAME, --hiddenimport MODULENAME`
Name an import not visible in the code of thescript(s). This option can be used multiple times.
`--additional-hooks-dir HOOKSPATH`
An additional path to search for hooks. This optioncan be used multiple times.
`--runtime-hook RUNTIME_HOOKS`
Path to a custom runtime hook file. A runtime hook iscode that is bundled with the executable and isexecuted before any other code or module to set upspecial features of the runtime environment. Thisoption can be used multiple times.
`--exclude-module EXCLUDES`
Optional module or package (the Python name, not thepath name) that will be ignored (as though it was notfound). This option can be used multiple times.
`--key KEY`	The key used to encrypt Python bytecode.

How to generate¶

`-d <all,imports,bootloader,noarchive>, --debug <all,imports,bootloader,noarchive>`
Provide assistance with debugging a frozenapplication. This argument may be provided multipletimes to select several of the following options. all: All three of the following options. imports: specify the -v option to the underlyingPython interpreter, causing it to print a messageeach time a module is initialized, showing theplace (filename or built-in module) from which itis loaded. Seehttps://docs.python.org/3/using/cmdline.html#id4. bootloader: tell the bootloader to issue progressmessages while initializing and starting thebundled app. Used to diagnose problems withmissing imports. noarchive: instead of storing all frozen Pythonsource files as an archive inside the resultingexecutable, store them as files in the resultingoutput directory.
`-s, --strip`	Apply a symbol-table strip to the executable andshared libs (not recommended for Windows)
`--noupx`	Do not use UPX even if it is available (worksdifferently between

Mac Run App As Admin By Default