There are a few nice automations here, but I think only Windows users could think this workflow makes sense. Renaming the .exe and then running it isn't really any easier than supplying the package name as an argument on the command line - which is the experience you'd already have with Pipx, except for the actual Python installation (which is easy on Windows). Further, Pipx would allow you to create the entry point in community standard ways. (For that matter, from what I can tell, almost everyone making CLI applications in Python is expecting POSIX-like command syntax, even when it runs on Windows - just like Python itself does. A hybrid command line like `python.exe -m your-package /polyinstall` looks very strange to me, and having it automatically wrapped up in a shortcut doesn't actually change that fact.)