Bug report

Appears to be new in 3.13.0a6, as I've been using it with a5 and it's only after updating that I noticed.

Basically, the venv's prefix and site-packages directories are not present insys.path when the base interpreter is from a Store install, and it has the user site. I need to investigate further to figure out exactly why.

Test code:

> python3 -m venv testenv --without-pip> testenv\Scripts\activate> python -m site# expect "$PWD\testenv\Scripts\Lib\site-packages" in list

If anyone wants to help check it out, the Store page for alpha releases ishttps://www.microsoft.com/store/apps/9PNRBTZXMB4Z

Linked PRs

• gh-117786: Fix venv created from Windows Store install by restoring __PYVENV_LAUNCHER__ smuggling #117814