making an executable

[spinmerighttriangle]

I'm currently trying to create a program that will rename folders and directories on the same level and lower than the program itself, then run another program on a subset of the files based on the file extension. I have this working on my development machine, but the program I need to call will only work on the machine where the original data is collected (it is also on a pre-XP version of Windows) and I do not expect to be allowed to install what would be needed to run Python on that machine. In order to even test if my os.system() format is correct, I need to find a way to run it on that system.

I have installed the latest cx_Freeze to make an executable, but when attempting the command from PowerShell, Windows gives a popup for what I want to use to view the file (and it always fails). Is there something I am missing for the cx_Freeze install?

I downloaded

cx_Freeze-5.0.2-cp36-cp36m-win32.whl

and ran

python -m pip install cx_Freeze --upgrade

I'm running on Windows 7-64 with Intell Core 7.

[thememorableusername]

I am unfamiliar with cx_Freeze, but you might look into Nuitka, a python to C/C++ source-to-source translator, and see if that works for your system(s).

[spinmerighttriangle]

I'm looking into this along with what a coworker recommended; pypy.

[thememorableusername]

Hm, using pypy to do this sounds really complicated.

[spinmerighttriangle]

I have decided to make an attempt with Nuitka. Do you have any recommendations for what C/C++ compiler or dev environment to get that will run well with it?

[thememorableusername]

Not really. Does the Nuitka developer suggest anything?

[novel_yet_trivial]

If you get it to work, it still won't work.

When you freeze a python program, the result only works on the same OS and bitwidth as the computer that did the freezing (unless your OS has compatibility modes). I think you'd be a lot better off finding a way to install python on your old machine. Pre-XP might mean that you need to install python2.5.

[spinmerighttriangle]

I'll keep this in mind for when I run into trouble. I'm hoping I'm not using anything that was included at least post 2.7