myscrip

file) on which the executable file depends) pyi-...: And so on. Use PyInstaller pyinstallerSyntax: pyinstaller [options] script [script ...] | specfile In the simplest usage, execute the command in the same directory as myscript. py: pyinstaller mycript.py Then we will see two newly added directories: build and dist. The files under dist are executable files that can be released. For the above commands, you will find a bunch of files under the dist directory, various dynamic library files and

insensitive-User: search by owner-Group: search by group-Uid: search by uid-Gid: search by gidIn the specified time range:-Atime: [+/-] N (access time): +-indicates --- (+) ---- N --- (-) ---- currentdayEg: find-atime-3-exec ls-l {}\;-Mtime: (modification time) Same as above-Ctime (change time) Same as above-Amin is in the same unit as preceding.-Mmin-Cmin-Access closer to anewer a.txt than a.txtEg: find-anewer sh01.sh-exec ls-l {}\;-Newer is equivalent to modification time-Cnewer is equivalent

--- (-) ---- currentdayEg: find-atime-3-exec ls-l {}\;-Mtime: (modification time) Same as above-Ctime (change time) Same as above-Amin is in the same unit as preceding.-Mmin-Cmin-Access closer to anewer a.txt than a.txtEg: find-anewer sh01.sh-exec ls-l {}\;-Newer is equivalent to modification time-Cnewer is equivalent to change time.-Type: search by typeD (directory), l (link file), f (common file), s (socket file ),B (Block device), c (character device), p (command pipeline file)Eg: find/var-t

-atime-3-execls-l {}\;-Mtime: (modificationtime) Same as above-Ctime (changetime) is the same as above-Amin is in the same unit as preceding.-Mmin-Cmin-Anewera.txtcloser access than a.txtEg: find-anewersh01.sh-execls-l {}\;-Newer is equivalent to modificationtime-Cnewer is equivalent to changetime.-Type: search by typeD (directory), l (link file), f (common file), s (socket file ),B (Block device), c (character device), p (command pipeline file)Eg: find/var-typel-execls-l {}\;-Size: search by si

When executing a pyInstaller command, a file is generated in the same directory as the script, which .spec tells Pyinstaller how to process all of your scripts and includes command options. Generally we don't have to bother with this file, if you need to package a data file, or add some Python run-time options to the packaged binary ... Some advanced packaging options require you to manually edit the .spec files. You can use:pyi-makespec options script [script ...]Using Pyinstallerpyi