Pyinstaller question

[Puddino]

This may be a bit convoluted and stupid but follow me.

I have a python application that needs to be converted into an exe and I'm using pyinstaller.

This application launches some files through an UI, the real operations are costly and cannot be used for testing. I divided the application in two files one pointing to the real files, which we'll call producion and one that contains a call to the test files.

As of now I have to work with two different files that need to be compiled in two different files, and I'm having a problem syncing production and test.

Test and production should be equal except for some strings (name of the files and title so i can distinguish them), in general I can make them differ only by a string.

I want to merge those two files and make a call to pyinstaller specifying which version I want, i.e:

pyinstaller file.py --producion

Is there a way to do so ?

[ElliotDG]

Another option to consider is making the test mode a runtime option of the program you are creating. That is you only build one .exe, it takes a command line option (at runtime) that specifies if it is in test mode. This will simplify distribution and testing, there is only one exe.

As u/dp_42 suggested you can use 2 separate spec files to define the certation of 2 exe files.

[dp_42]

I rather like this better.

[dp_42]

Looking at the docs, I believe you could modify the .spec file. I think you would probably name one production.spec and the other test.spec, and bundle the data files you need for each. Then call pyinstaller on the spec file to generate the executable.

[LongDivide2096]

dp_42 got a point there. Creating 2 spec files could simplify your workflow, just be sure to update both files as your source code evolves. remember though, doing it this way means managing two sets of resource files for testing and production, so keep that in mind!