r/Python • u/AutoModerator • 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:
Open Mic: Share your thoughts, questions, or anything you'd like related to Python or the community.
Community Pulse: Discuss what you feel is working well or what could be improved in the /r/python community.
News & Updates: Keep up-to-date with the latest in Python and share any news you find interesting.
Guidelines:
All topics should be related to Python or the /r/python community.
Be respectful and follow Reddit's Code of Conduct.
Example Topics:
New Python Release: What do you think about the new features in Python 3.11?
Community Events: Any Python meetups or webinars coming up?
Learning Resources: Found a great Python tutorial? Share it here!
Job Market: How has Python impacted your career?
Hot Takes: Got a controversial Python opinion? Let's hear it!
Community Ideas: Something you'd like to see us do? tell us.
Let's keep the conversation going. Happy discussing! 🌟
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:
Build CPython from source ourselves.
Migrate all production workloads to a newer minor version.
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?