Store python interoperates poorly with common dev tools (vscode+mypy, git-bash, cygwin,)

I had a brief chat on twitter with @zooba about this.

Bug report

The MS Store version of Python has something about it (sorry for vagueness - don't know the cause) that means existing software fails to invoke it with a "Permission Denied" error. Stackoverflow and other forums are full of these reports, with folk 'fixing' the problem by uninstalling the store version, or mucking with PATH etc to put the 'normal' installed version ahead on the PATH.

I recognize that this may be caused by something outside cpythons direct control, but there seems to be a cluster of programs with issues, and significant developer friction encountered, so if we can do anything to make the experience better (e.g. fund other projects to deal with the consequences of our choice, or ask MS to allow better interop between store and non-store programs or some such), that would be great.

Specific cases I've encountered:

• git-bash within vscode, running 'python' or 'pip' etc in the terminal window results in that error. Similarly when invoked from with Makefiles and so on.

• mypy extension for vscode installed; the mypy extension fails to find dmypy installed via the store python's pip.

• poetry also fails with the MS store python version but a different error (they have a cluster of bugs - https://github.com/python-poetry/poetry/issues/2746 and similar with attempts to state non-existing files) - I think these are a different but perhaps related problem.

Your environment

Windows 11 up to date, Python 3.9 from the store.

Comienza reproduciendo el comportamiento Permission Denied en Windows 11 con Microsoft Store Python en el terminal git-bash de VS Code, incluida la extensión mypy y las herramientas instaladas mediante pip. El issue no menciona archivos ni pruebas de CPython; para darlo por terminado sería necesario identificar una mejora concreta y validada de la interoperabilidad o documentar que es necesaria la coordinación con las herramientas afectadas o con Microsoft.