Skip to content

PyManager packaging of 3.11-3.12 has broken venv scripts #135455

Closed
@zooba

Description

@zooba

See python/pymanager#133

In short, by using the new PC/layout script against older versions, a rename that used to be performed at build time was skipped. As a result, the republished 3.11 and 3.12 packages have a non-functional venv module on Windows.

Once the script is fixed (and tested more thoroughly), I'll repackage and republish the 3.11 and 3.12 releases. This will update their hashes, but should update the feed as well so that it still all matches. That's what beta is for I guess.

The fix won't need to be backported, because repackaging uses the script from main (which was fundamentally the root cause). I'll do a full diff between the old and current version of the scripts to see if any other changes slipped through, but I don't think there was anything that wasn't purely additive.

FYI @pablogsal and @Yhg1s as RMs for the affected releases. Nothing for you to worry about, though.

Linked PRs

Metadata

Metadata

Assignees

Labels

3.11only security fixes3.12only security fixesstdlibPython modules in the Lib dirtopic-installationtopic-venvRelated to the venv module

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions