-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Comments
I'll give this a shot. |
LexiconCode
added a commit
to LexiconCode/natlink
that referenced
this issue
Apr 20, 2024
astral-sh/python-build-standalone#221 - update cpython versions
LexiconCode
added a commit
to LexiconCode/natlink
that referenced
this issue
Apr 20, 2024
astral-sh/python-build-standalone#221 - update cpython versions
LexiconCode
added a commit
to LexiconCode/natlink
that referenced
this issue
Apr 20, 2024
astral-sh/python-build-standalone#221 - update cpython versions
LexiconCode
added a commit
to dictation-toolbox/natlink
that referenced
this issue
Apr 26, 2024
astral-sh/python-build-standalone#221 - update cpython versions
LexiconCode
added a commit
to LexiconCode/natlink
that referenced
this issue
Jun 1, 2024
astral-sh/python-build-standalone#221 - update cpython versions
LexiconCode
added a commit
to LexiconCode/natlink
that referenced
this issue
Aug 23, 2024
astral-sh/python-build-standalone#221 - update cpython versions
LexiconCode
added a commit
to LexiconCode/natlink
that referenced
this issue
Aug 23, 2024
astral-sh/python-build-standalone#221 - update cpython versions
LexiconCode
added a commit
to LexiconCode/natlink
that referenced
this issue
Mar 1, 2025
astral-sh/python-build-standalone#221 - update cpython versions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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.
The text was updated successfully, but these errors were encountered: