venv with Windows Store base does not have correct sys.path

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 in sys.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 is https://www.microsoft.com/store/apps/9PNRBTZXMB4Z

Linked PRs

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

Oh right, I did the venvlauncher refactoring for this alpha, so the breakage is 100% my fault 😆

Part of that change was to stop smuggling __PYVENV_LAUNCHER__, but also to stop rewriting argv[0]. Those two should have cancelled each other out, but I guess with the Store packaging it doesn't.

pythongh-117786: Fix venv created from Windows Store install by resto…

Merge remote-tracking branch 'upstream/main' into pythongh-117786

Merge branch 'main' into pythongh-117786

gh-117786: Fix venv created from Windows Store install by restoring _…

Navigation Menu

Repository navigation

venv with Windows Store base does not have correct sys.path #117786

Bug report

Linked PRs

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

venv with Windows Store base does not have correct sys.path #117786

Description

Bug report

Linked PRs

Activity

zooba commented on Apr 11, 2024

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions