installer VS py2exe

And probably https://github.com/pradyunsg/installer https://pypi.org/project/installer/ too, but that one isn't under the pypa org yet, given the author, it probably will be.

All that being said, the deprecations and removals are being done way before the replacements are in place and tested and features/rough edges rounded out, which I guess is python tradition at this point.

IMHO, the repos maintained by pypa should all be part of the core teams responsibility (e.g. pip is maintained by pypa, not core, but its installed as part of the python installer you download from the foundation's website...), along with solving building/installing/packaging/distributing as a whole. But the core team decided their volunteers didn't want to work on that (ok fair) and pypa stepped up to do it, but never really had enough manpower to tackle it well (ok also fair). And none of the tech companies ever thought "gee we rely so heavily on this awesome tool, maybe we should send them some money to keep the lights on..." So instead its just been a giant mess.

python -m installer --destdir="$pkgdir" once pradyunsg/installer#66 is finally merged

See this GitHub issue to follow the relevant discussion and development.

There are ways to bundle Python with your application using something like py2exe

Then you can turn the python program to an actual executable, a normal .exe file that user just launches and uses. If you chose to use this way, look into PyInstaller or py2exe. The executables will be obviously bigger, I think at least PyInstaller pretty much just packages Python and your script into .exe to make it work, so every program would be quite big (as each program has its own Python packaged). I also heard the process of turning the scripts to .exe is sometimes a bit problematic if you use some fancy imports and you also might run into problems with architecture.

*fyi, you can use a tool like py2exe or PyInstaller to convert Python scripts into a Windows Executable.

py2exe