Thanks! This is a great idea.

I'd prioritise adding support to the Store app first, as that's easier to manage (we're not having to modify files owned by other apps outside of our install directory). But no reason we couldn't extend the older installer and make that do it as well.

We probably want to experiment a bit with what goes into it. I think this should probably be a single profile that uses the default Python (whatever "python.exe" maps to), but it could also be a Powershell/Cmd shell that has PATH set (though *that* is redundant with the Store package, so perhaps better for the regular installer).

I *really* don't want to fill up Terminal with one (or more) profiles for each Python version. I'm trying to motivate other work to make it easier for users to have multiple installs but one consistent default, so I'd rather not multiplex here.