Skip to content

Drop support for Windows static builds #221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
indygreg opened this issue Feb 28, 2024 · 1 comment · Fixed by #234
Closed

Drop support for Windows static builds #221

indygreg opened this issue Feb 28, 2024 · 1 comment · Fixed by #234

Comments

@indygreg
Copy link
Collaborator

I started this project in support of PyOxidizer. And one of the reasons I started PyOxidizer was to see if it was possible to achieve single file executable Python applications.

While I arguably succeeded in accomplishing that single file executable goal, it came at a prohibitively high cost of being effectively unusable in many situations. The further I diverged from common Python practices, the more difficult it was to get PyOxidizer to work.

The Windows static builds in this project are an artifact from trying to achieve the original goals of PyOxidizer.

With the benefit of hindsight, the static Windows builds are borderline unusable. They have many known (and likely several unknown) quirks. I don't believe they are providing much value.

Over the history of this project, here are download statistics for the Windows static builds:

Build Install Only Download Count
i686-pc-windows-msvc-static 668
i686-pc-windows-msvc-shared 1039
x86_64-pc-windows-msvc-static 12792
x86_64-pc-windows-msvc-shared 914998
Build Full Archive Download Count
i686-pc-windows-msvc-static-noopt 85226
i686-pc-windows-msvc-shared-pgo 91420
x86_64-pc-windows-msvc-static-noopt 83895
x86_64-pc-windows-msvc-shared-pgo 135683

I reckon PyOxidizer is the biggest driver of the full archive downloads. And there we see that the static archives are relatively popular. But probably because PyOxidizer defaulted to using the Windows static builds in various releases.

The install only archives - which customers organically adopt - tells a different story. Here, shared is getting 71x the downloads as static.

The static Windows builds constitute a non-trivial amount of complexity to continue maintaining. The distributions break tons of assumptions made by Python projects in the wild. I think they are more trouble to support than they are worth.

So I'm proposing we stop supporting the Windows static builds.

Please leave a comment with objections if you have any.

In the absence of compelling arguments to preserve them, the Windows static distributions will be removed in a future release.

@charliermarsh
Copy link
Member

I'll give this a shot.

LexiconCode added a commit to LexiconCode/natlink that referenced this issue Apr 20, 2024
LexiconCode added a commit to LexiconCode/natlink that referenced this issue Apr 20, 2024
LexiconCode added a commit to LexiconCode/natlink that referenced this issue Apr 20, 2024
LexiconCode added a commit to dictation-toolbox/natlink that referenced this issue Apr 26, 2024
LexiconCode added a commit to LexiconCode/natlink that referenced this issue Jun 1, 2024
LexiconCode added a commit to LexiconCode/natlink that referenced this issue Aug 23, 2024
LexiconCode added a commit to LexiconCode/natlink that referenced this issue Aug 23, 2024
LexiconCode added a commit to LexiconCode/natlink that referenced this issue Mar 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants