-
Hey, The PyInstaller Django recipe produces an .exe that can be run like a regular Django app, using the command-line flag pyinstaller --name=mysite mysite/manage.py
mysite.exe runserver Can PyInstaller be configured to pass runtime flags automatically, so they don't have to be specified by the user? Something like this, perhaps: pyinstaller --name=mysite mysite/manage.py --flags runserver
mysite.exe I assume the next-best way would be to write a wrapper around |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I'd definitely prefer people to either make their own wrapper or just put something like: sys.argv = sys.argv[:2] + ["builtin", "options"] + sys.argv[2:] near the top of their code. I doubt building it into PyInstaller would get far before people start requesting |
Beta Was this translation helpful? Give feedback.
I'd definitely prefer people to either make their own wrapper or just put something like:
near the top of their code.
I doubt building it into PyInstaller would get far before people start requesting
~
and environment variable expansions, platform abstractions, templating variables (e.g. current working directory or app location) and some secret override to get back to the raw original CLI mode. At least if you do it, that's all your problem. 🙂