Documentation: Clarify state of python static builds on Windows

The current docs say that Windows Static Distributions are Extremely Brittle.
However, what are these static builds? For example, there is #221, basically suggesting that static Windows builds are no longer a thing, concluded with #234.
This suggests to me that the docs are not up to date at this point. Any improvement of the docs would be greatly appreciated here.

Yes, we removed support for these. Pull request welcome.

Does this mean that this section can just be dropped? Or are there still some things we have to take note of when using these Python builds instead of the vanilla CPython builds?
Quick tests with nvda, for example, revealed an access violation with comtypes, though I do not yet have more details than just the reported crash.

Docs: remove Windows static build quirk (#598)

Just a quick one. To add support for pip on Windows I added a pip.cmd next to python.exe with the following contents

@echo off
setlocal
"%~dp0python.exe" -m pip %*
IF %ERRORLEVEL% NEQ 0 EXIT /b %ERRORLEVEL%
endlocal

This makes pip available in the terminal.

Does this mean we won't see python builds for Windows beyond 3.14?

There are going to be Windows Python builds, they're just dynamically linked instead os statically.

Navigation Menu

Repository navigation

Documentation: Clarify state of python static builds on Windows #597

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Documentation: Clarify state of python static builds on Windows #597

Description

Activity

zanieb commented on Apr 29, 2025

LeonarddeR commented on Apr 29, 2025

alshdavid commented on May 18, 2025

zanieb commented on May 18, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions