compiler – Python command-line tool for compiling py files into executable files on Mac

When I was using a computer, I was familiar with py2exe, the mac equivalent that I saw talking about was mostly py2app – which compiles python into .app files and not into .exec files. I was familiar with compiling C files for mac execs, and I had heard of cython (but I had never used it before). I thought I could write something to go from python to cython and an exec. Initially, I did not write this for anyone else, but I am now thinking of packaging it as a pip module.

This is the first time I've built a command-line tool to run shell commands and manipulate files and directories.

"" "(PYCX) PYthon to Cython to eXec, a unix command-line utility
Use:
pycx FILES ... [-o DIR --show --delete --run]
  pycx --help

options:
FILE one or more python files to compile
-o --output = DIR output directory
-s --show shows the result of the compilation of the executive
-d --delete deletes the file c after compiling the exec
-r --run launches the exec after compiling
-h --help shows this screen.
"" "
import os, re
from docopt import docopt

args = docopt (__ doc__)

# the two paths below tell gcc where is python so that cython can be compiled into exec
INCLUDES = & # 39; /usr/local/opt/python/Frameworks/Python.framework/Versions/3.7/include/python3.7m'
LIBRARY = & # 39; /usr/local/Cellar/python/3.7.2_2/Frameworks/Python.framework/Versions/3.7/lib'
HIDEDATA = & # 39; &> / dev / null & # 39; # This is used to hide the output when compiling C files

for pyFILE in args['FILES']:
if pyFILE.endswith (& # 39 ;. py): # file must be a python file
path, name = os.path.split (pyFILE) # divide the full path into a separate path and file name

cFILE = re.sub (# pg $, # pf #), # filename with the .c extension and path
FILE = re.sub ( # Py $, ###, name) # file name without extension or path

PATH = path + & # 39; / & # 39; if path is not & # 39; else & # 39;. & # 39; # if in the current directory, path = & # 39;. & # 39;
OUTPUT = args['--output'] + & # 39; / & # 39; if args['--output'] else & # 39; & # 39; # blank if no argument is given
SHOW = HIDEDATA otherwise args['--show'] else & # 39; & # 39; # will hide the gcc output if SHOW is false
# this command will be used to delete the C file
DELETE = find {PATH} -name "{FILE} .c" -type f | xargs rm -f if args['--delete'] other & # 39; & # 39;
RUN = f. / {OUTPUT} {FILE} & # 39; if args['--run'] else & # 39; & # 39; # command to run the exec

orders = [  # cython to make C file, gcc to compile to exec, and some options
            f"cython --embed -o {cFILE} {pyFILE}",  # convert python to cython C file
            # compile cython C file to exec file
            f"gcc -v -Os -I {INCLUDES} -L {LIBRARY} {cFILE} -o {OUTPUT}{FILE} " + 
            # source python & other options -- hide or show, delete C file, run exec
            f"-lpython3.7 -lpthread -lm -lutil -ldl {SHOW}", f"{DELETE}", f"{RUN}"
        ]
        for order in orders:
os.system (command) # execute the commands above, excluding empty commands
other:
print (__ doc__) # displays the help menu if the user does not put a python file

In addition to the modification INCLUDES and LIBRARY to work with different path locations, are there any other major issues preventing this from working as a python module? Does it even look like a tool that some people might use?