r/Python • • 18d ago

Daily Thread Friday Daily Thread: r/Python Meta and Free-Talk Fridays

Weekly Thread: Meta Discussions and Free Talk Friday 🎙️

Welcome to Free Talk Friday on /r/Python! This is the place to discuss the r/Python community (meta discussions), Python news, projects, or anything else Python-related!

How it Works:

  1. Open Mic: Share your thoughts, questions, or anything you'd like related to Python or the community.

  2. Community Pulse: Discuss what you feel is working well or what could be improved in the /r/python community.

  3. News & Updates: Keep up-to-date with the latest in Python and share any news you find interesting.

Guidelines:

Example Topics:

  1. New Python Release: What do you think about the new features in Python 3.11?

  2. Community Events: Any Python meetups or webinars coming up?

  3. Learning Resources: Found a great Python tutorial? Share it here!

  4. Job Market: How has Python impacted your career?

  5. Hot Takes: Got a controversial Python opinion? Let's hear it!

  6. Community Ideas: Something you'd like to see us do? tell us.

Let's keep the conversation going. Happy discussing! 🌟

18 Upvotes

2 comments sorted by

9

u/Defiant_Respect9500 17d ago

I'd like to ask about the lack of Windows installers for Python security-only releases.

As I understand it, Python versions receive regular bugfix releases with binary installers for approximately 18 months, after which they enter the security-only phase, where releases are source-only.

For those of us maintaining Python applications and automation scripts on Windows servers, this creates a rather awkward situation.

We have dozens of production scripts with various third-party dependencies, including native extensions. Upgrading to a newer Python minor version requires compatibility testing across all these scripts and dependencies.

However, once the current version enters its security-only phase, we can no longer install security updates using official Windows binaries.

That effectively leaves us with three options:

  1. Build CPython from source ourselves.

  2. Migrate all production workloads to a newer minor version.

  3. Continue running an older patch release despite available security fixes.

None of these seems particularly attractive, especially in environments with strict security and change-management requirements.

Is there a technical or organizational reason why official Windows installers cannot continue to be provided during the security-only phase?

And has the Python team considered extending the period during which binary installers are available, or providing another officially supported way to deploy security fixes on Windows without requiring a minor-version upgrade?

1

u/Discordbothost 12d ago

the short version is that the core team's binary builds and installers are tied to the bugfix phase, and security-only releases are source-only on purpose, so there's no official fix for that gap. you're really left with your three options, but there are cheaper ways to do the first one than it sounds:

  • build from source in CI once per security release. PCbuild\build.bat is fairly painless, and then you just zip the output and deploy it the same way on every server

  • pull a prebuilt interpreter from somewhere that tracks patch releases. uv (python-build-standalone) and conda-forge both ship Windows builds, though check that your specific old minor is still covered, I wouldn't assume

  • keep each script in its own venv and treat the minor-version bump as a yearly chore instead of a one-off emergency. a CI matrix on the next minor means the test pass is mostly done by the time you need it

the third thing (staying on an unpatched interpreter) is the one i'd rule out first if you have change-management requirements.