Re: [PyInstaller] Creating Single Executable for Kivy Files

I have not had any success building a single file executable with Kivy. I have been successfully in built a number of apps using the directory model.  I then use Inno Setuphttp://www.jrsoftware.org/isinfo.php , to pack the directory and executable into a

[PyInstaller] .py files are in the dist directory

Is it possible to have a one folder build without the source *.py files included in the distribution directory? I have attached my spec file. If I add *.py to the exclude in COLLECT, the application will not run. I have built an application that uses Kivy, and runs on Windows. The spec file

[PyInstaller] Re: PyInstaller-3.3.1: Operational Windows build inconsistent

Here are a few things to consider: On the two machines, are the executables being run from the same spot? Is your program making assumptions about files and the current directory? If the -F option did not work, you would need the contents of the full build directory on each machine. You do

Re: [PyInstaller] failed to create process

Start by building in the directory mode instead of the one file mode. There are some logs that get created in the build directory that might be helpful. Sent from my iPhone > On May 29, 2019, at 12:50 PM, Patrick Carra wrote: > > I installed python 3.7 and installed pyintaller via pip using

RE: [PyInstaller] win32com.client Issues

... Since I'm building a one-folder bundle, my file locations should be correct with the pyinstaller defaults, no? Regards, Ben On Sat, May 4, 2019 at 5:35 AM Elliot Garbus wrote: Are you doing a single file build or a directory build?  You need to tell Pyinstaller where the files

RE: [PyInstaller] win32com.client Issues

Are you doing a single file build or a directory build? You need to tell Pyinstaller where the files are located. Read the section in the docs on runtime information. https://pyinstaller.readthedocs.io/en/stable/runtime-information.html When your program is not frozen, the standard Python

[PyInstaller] Re: Set python command option -OO

Thank you - that is very helpful. The desire to remove doc-strings has to do with their desire to keep things "more secure". I'm also building a portion of the app in cython, for the same reason. This is a direct request of my client. I'll look for a different path to disable asserts and

[PyInstaller] Re: Set python command option -OO

This worked: python -OO -m PyInstaller --clean -y .\my-specfile.spec On Saturday, January 20, 2024 at 4:15:15 PM UTC-7 Elliot Garbus wrote: > Thank you - that is very helpful. > The desire to remove doc-strings has to do with their desire to keep > things "more secure".

[PyInstaller] Set python command option -OO

How do I set the python command line option -OO. The objective is to disable assert statements and remove docstrings. Looking here: Using Spec Files — PyInstaller 6.3.0 documentation It appears the -OO

[PyInstaller] Re: How to avoid .pyc files from executable generation

Pyinstaller works by bundling the .pyc files. If you want to hide your source code more complely you could compile some of you python modules with Cython to c. See: https://pyinstaller.org/en/stable/operating-mode.html#hiding-the-source-code On Tuesday, April 23, 2024 at 12:57:16 PM UTC-7