https://www.python.org/downloads/release/python-3150a2/ Python 3.15 is still in development. This release, 3.15.0a2, is the second of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2026-05-05) and, if necessary, may be modified or deleted up until the release candidate phase (2026-07-28). Please keep in mind that this is a preview release and its use is recommended for production environments. Many new features for Python 3.15 are still being planned and written. Among the new major new features and changes so far: The next pre-release of Python 3.15 will be 3.15.0a3, currently scheduled for 2025-12-16. “An hour,” said Ahab, standing rooted in his boat’s stern; and he gazed beyond the whale’s place, towards the dim blue spaces and wide wooing vacancies to leeward. It was only an instant; for again his eyes seemed whirling round in his head as he swept the watery circle. The breeze now freshened; the sea began to swell. “The birds!—the birds!” cried Tashtego. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the . Python Software Foundation Regards from a crisp and sunny subzero Helsinki, Your release team, Hugo van Kemenade Ned Deily Steve Dower Å�ukasz Langa

https://www.python.org/downloads/release/python-3150a1/ Python 3.15 is still in development. This release, 3.15.0a1, is the first of seven planned alpha releases. Alpha releases are intended to make it easier to test the current state of new features and bug fixes and to test the release process. During the alpha phase, features may be added up until the start of the beta phase (2026-05-05) and, if necessary, may be modified or deleted up until the release candidate phase (2026-07-28). Please keep in mind that this is a preview release and its use is recommended for production environments. Many new features for Python 3.15 are still being planned and written. Among the new major new features and changes so far: The next pre-release of Python 3.15 will be 3.15.0a2, currently scheduled for 2025-11-18. And hence not only at substantiated times, upon well known separate feeding-grounds, could Ahab hope to encounter his prey; but in crossing the widest expanses of water between those grounds he could, by his art, so place and time himself on his way, as even then not to be wholly without prospect of a meeting. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the . Python Software Foundation Regards from Helsinki before the first PyCon Finland in 9 years, Your release team, Hugo van Kemenade Ned Deily Steve Dower �ukasz Langa

There are no other changes in this release, compared to 3.13.8. Thanks to all of the many volunteers who help make Python Development and this release possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the . Python Software Foundation Your expedited release team, Your release team, Thomas Wouters Ned Deily Steve Dower �ukasz Langa

We couldn’t just let Hugo have fun with 3.14.0, so here are new security releases of the venerated Python versions, 3.12 through 3.9! Additional security content in this release: Additional security content in this release: Additional security content in this release: As always, upgrading is highly recommended to all users of affected versions. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. Regards from your tireless release team, Thomas Wouters Pablo Galindo Salgado Å�ukasz Langa Ned Deily Steve Dower

python.org/downloads/release/python-3140/ Python 3.14.0 is the newest major release of the Python programming language, and it contains many new features and optimisations compared to Python 3.13. Some of the major new features and changes in Python 3.14 are: For more details on the changes to Python 3.14, see . What’s new in Python 3.14 The installer we offer for Windows is being replaced by our new install manager, which can be installed from or from its . See for more information. The JSON file available for download contains the list of all the installable packages available as part of this release, including file URLs and hashes, but is not required to install the latest release. The traditional installer will remain available throughout the 3.14 and 3.15 releases. the Windows Store download page our documentation Edgar Allen Poe died on 7th October 1849. As we all recall from , piphilology is the creation of mnemonics to help memorise the digits of , and the number of letters in each word in a pi-poem (or “piem”) successively correspond to the digits of . 3.14.0a1 In 1995, Mike Keith, an American mathematician and author of constrained writing, retold Poe’s as a 740-word piem. Here’s the first two stanzas of : Near A Raven Midnights so dreary, tired and weary.     Silently pondering volumes extolling all by-now obsolete lore. During my rather long nap - the weirdest tap!     An ominous vibrating sound disturbing my chamber’s antedoor.         “This”, I whispered quietly, “I ignore”. Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the . Python Software Foundation Regards from a colourful autumnal Helsinki, Your release team, Hugo van Kemenade Ned Deily Steve Dower Å�ukasz Langa

The latest version of Python 3.13 is now available! Python 3.13 is the previous major release of the Python programming language, and it contains many new features and optimizations compared to Python 3.12. 3.13.8 is the eighth maintenance release of 3.13, containing around 200 bugfixes, build improvements and documentation changes since 3.13.7. Full Changelog Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation. Regards from your package managers,

It’s 🪄 🪄 the final 3.14 release candidate! https://www.python.org/downloads/release/python-3140rc3/ The ABI isn’t changing. Wheels built for rc1 should be fine for rc2, rc3 and 3.14.x, so this shouldn’t affect too many people. This release, , is the final release preview. Entering the release candidate phase, only reviewed code changes which are clear bug fixes are allowed between this release candidate and the final release. The next release of Python 3.14 will be the final release, 3.14.0, scheduled for Tuesday, 2025-10-07. There will be from this point forward in the 3.14 series, and the goal is that there will be as few code changes as possible. We maintainers of third-party Python projects to prepare their projects for 3.14 during this phase, and publish Python 3.14 wheels on PyPI to be ready for the final release of 3.14.0, and to help other projects do their own testing. Any binary wheels built against Python 3.14.0 release candidates with future versions of Python 3.14. As always, report any issues to . the Python bug tracker Please keep in mind that this is a preview release and while it’s as close to the final release as we can get it, its use is recommended for production environments. Some of the major new features and changes in Python 3.14 are: For more details on the changes to Python 3.14, see . What’s new in Python 3.14 The installer we offer for Windows is being replaced by our new install manager, which can be installed from or from its . See for more information. The JSON file available for download below contains the list of all the installable packages available as part of this release, including file URLs and hashes, but is not required to install the latest release. The traditional installer will remain available throughout the 3.14 and 3.15 releases. the Windows Store download page our documentation According to Pablo Galindo Salgado at : PyCon Greece Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organisation contributions to the . Python Software Foundation Regards from wonderful Cambridge, Your release team, Hugo van Kemenade Ned Deily Steve Dower Å�ukasz Langa Savannah Ostrowski

The 2026 DSF Board Election has closed, and the following candidates have been elected: Jacob Kaplan-Moss Priya Pahwa Ryan Cheley They will all serve two years for their term. 2026 Board Directors elected for the 2025 DSF Board - Abigail Gbadago, Jeff Triplett, Paolo Melchiorre, Tom Carrick - are continuing with one year left to serve on the board. Therefore, the combined 2026 DSF Board of Directors are: Abigail Gbadago Jacob Kaplan-Moss* Jeff Triplett Paolo Melchiorre Priya Pahwa* Ryan Cheley* Tom Carrick * Elected to a two year term Congratulations to our winners, and a huge thank you to our departing board members Sarah Abderemane and Thibaud Colas. Thank you again to everyone who nominated themselves. Even if you were not successful, you gave our community the chance to make their voices heard in who they wanted to represent them.

For November 2025, we welcome Akio Ogasahara as our DSF member of the month! ⭐ Akio is a technical writer and systems engineer. He contributed to the Japanese translation for many years. He has been a DSF member since June 2025. You can learn more about Akio by visiting Akio's X account and his GitHub Profile. Let’s spend some time getting to know Akio better! Can you tell us a little about yourself (hobbies, education, etc.) I was born in 1986 in Rochester, Minnesota, to Japanese parents, and I’ve lived in Japan since I was one. I’ve been fascinated by machines for as long as I can remember. I hold a master’s degree in mechanical engineering. I’ve worked as a technical writer and a software PM, and I’m currently in QA at a Japanese manufacturer. I'm curious, where does your nickname “libratech” come from? I often used “Libra” as a handle because the symbol of Libra—a balanced scale—reflects a value I care deeply about: fairness in judgment. I combined that with “tech,” from “tech writer,” to create “libratech.” How did you start using Django? Over ten years ago, I joined a hands-on workshop using a Raspberry Pi to visualize sensor data, and we built the dashboard with Django. That was my first real experience. What other framework do you know and if there is anything you would like to have in Django if you had magical powers? I’ve used Flask and FastAPI. If I could wish for anything, I’d love “one-click” deployment that turns a Django project into an ultra-lightweight app running on Cloudflare Workers. What projects are you working on now? As a QA engineer, I’m building Pandas pipelines for quality-data cleansing and creating BI dashboards. What are you learning about these days? I’m studying for two Japanese certifications: the Database Specialist exam and the Quality Control Examination (QC Kentei). Which Django libraries are your favorite (core or 3rd party)? Django admin, without question. In real operations, websites aren’t run only by programmers—most teams eventually need CRM-like capabilities. Django admin maps beautifully to that practical reality. What are the top three things in Django that you like? Django admin Strong security DRY by design You have contributed a lot on the Japanese documentation, what made you contribute to translate for the Japanese language in the first place? I went through several joint surgeries and suddenly had a lot of time. I’d always wanted to contribute to open source, but I knew my coding skills weren’t my strongest asset. I did, however, have years of experience writing manuals—so translation felt like a meaningful way to help. Do you have any advice for people who could be hesitant to contribute to translation of Django documentation? Translation has fewer strict rules than code contributions, and you can start simply by creating a Transifex account. If a passage feels unclear, improve it! And if you have questions, the Django-ja translation team is happy to help on our Discord. I know you have some interest in AI as a technical writer, do you have an idea on how Django could evolve with AI? Today’s AI is excellent at working with existing code—spotting N+1 queries or refactoring SQL without changing behavior. But code written entirely by AI often has weak security. That’s why solid unit tests and Django’s strong security guardrails will remain essential: they let us harness AI’s creativity safely. Django is celebrating its 20th anniversary, do you have a nice story to share? The surgeries were tough, but they led me to documentation translation, which reconnected me with both English and Django. I’m grateful for that path. What are your hobbies or what do you do when you’re not working? Outside of computers, I enjoy playing drums in a band and watching musicals and stage plays! 🎵 Is there anything else you’d like to say? If you ever visit Japan, of course sushi and ramen are great—but don’t miss the sweets and ice creams you can find at local supermarkets and convenience stores! They’re inexpensive, come in countless varieties, and I’m sure you’ll discover a new favorite!🍦 Thank you for doing the interview, Akio !

On November 16th 2005, Django co-creator Adrian Holovaty announced the first ever Django release, Django 0.90. Twenty years later, today here we are shipping the first release candidate of Django 6.0 🚀. Since we’re celebrating Django’s 20th birthday this year, here are a few release-related numbers that represent Django’s history: 447 releases over 20 years. That’s about 22 per year on average. We’re at 38 so far for 2025. Fun fact: 33 of those releases predate PyPI, and were published via the Django website only! 131 security vulnerabilities addressed in those Django releases. Our security issues archive is a testament to our stellar track-record. 262,203 releases of Django-related packages. Django’s community ecosystem is gigantic. There’s tens of releases of Django packages per day as of 2025. There were 52 just today. With the caveat this depends a lot on what you classify as a "Django" package. This is what decades’ worth of a stable framework looks like. Expect more gradual improvements and bug fixes over the next twenty years’ worth of releases. And if you like this kind of data, check out the State of Django 2025 report by JetBrains, with lots of statistics on our ecosystem (and there’s a Get PyCharm Pro with 30 % Off & Support Django offer). Support Django If you or your employer counts on Django’s 20 years of stability, consider whether you can support the project via donations to our non-profit Django Software Foundation. Donate on the Django website Donate on GitHub sponsors Check out how to become a Corporate Member Once you’ve done it, post with #DjangoBirthday and tag us on Mastodon / on Bluesky / on X / on LinkedIn so we can say thank you! 59% Of our US $300,000.00 goal for 2025, as of November 19th, 2025, we are at: 58.7% funded $176,098.60 donated Donate to support Django

Django 6.0 release candidate 1 is now available. It represents the final opportunity for you to try out a mosaic of modern tools and thoughtful design before Django 6.0 is released. The release candidate stage marks the string freeze and the call for translators to submit translations. Provided no major bugs are discovered that can't be solved in the next two weeks, Django 6.0 will be released on or around December 3. Any delays will be communicated on the on the Django forum. Please use this opportunity to help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the release candidate package from our downloads page or on PyPI. The PGP key ID used for this release is Natalia Bidart: 2EE82A8D9470983E

For the last decade and more, we've been bundling CSS and JavaScript files. These build tools allowed us to utilize new browser capabilities in CSS and JS while still supporting older browsers. They also helped with client-side network performance, minimizing the content to be as small as possible and combining files into one large bundle to reduce network handshakes. We've gone through a lot of build tools iterations in the process; from Grunt (2012) to Gulp (2013) to Webpack (2014) to Parcel (2017) to esbuild (2020) and Vite (2020). And with modern browser technologies there is less need for these build tools. Modern CSS supports many of the features natively that the build tools were created for. CSS nesting to organize code, variables, @supports for feature detection. JavaScript ES6 / ES2015 was a big step forward, and the language has been progressing steadily ever since. It now has native module support with the import / export keywords Meanwhile, with HTTP/2 performance improvements, parallel requests can be made over the same connection, removing the constraints of the HTTP/1.x protocol. These build processes are complex, particularly for beginners to Django. The tools and associated best practices move quickly. There is a lot to learn and you need to understand how to utilize them with your Django project. You can build a workflow that stores the build results in your static folder, but there is no core Django support for a build pipeline, so this largely requires selecting from a number of third party packages and integrating them into your project. The benefit this complexity adds is no longer as clear cut, especially for beginners. There are still advantages to build tools, but you can can create professional results without having to use or learn any build processes. Build-free JavaScript tutorial To demonstrate modern capabilities, let's expand Django’s polls tutorial with some newer JavaScript. We’ll use modern JS modules and we won’t require a build system. To give us a reason to need JS let's add a new requirement to the polls; to allow our users to add their own suggestions, instead of only being able to vote on the existing options. We update our form to have a new option under the selection code: or add your own <input type="text" name="choice_text" maxlength="200" /> Now our users can add their own options to polls if the existing ones don't fit. We can update our voting view to handle this new option, with more validation: If there is no vote selection we handle adding the new option If there is no vote selection nor a new choice_text, we show an error Also show an error if both are selected. With our logic getting more complex it would be nicer if we had some JavaScript to do this. We can build a script that handles some of the form validation for us. // Note the "export default" to make this function available for other modules. export default function initFormValidation() { document.getElementById("polls").addEventListener("submit", function (e) { const choices = this.querySelectorAll('input[name="choice"]'); const choiceText = this.querySelector('input[name="choice_text"]'); const hasChecked = [...choices].some(r => r.checked); const hasText = choiceText?.value.trim() !== ""; if (!hasChecked && !hasText) { e.preventDefault(); alert("You didn't select a choice or provide a new one."); } if (hasChecked && hasText) { e.preventDefault(); alert("You can't select a choice and also provide a new option."); } }); } Note how we use export default in the above code. This means form_validation.js is a JavaScript module. When we create our main.js file, we can import it with the import statement: import initFormValidation from "./form_validation.js"; initFormValidation(); Lastly, we add the script to the bottom of our details.html file, using Django’s usual static template tag. Note the type="module" this is needed to tell the browser we will be using import/export statements. <script type="module" src="{% static 'polls/js/main.js' %}"></script> That’s it! We got the modularity benefits of modern JavaScript without needing any build process. The browser handles the module loading for us. And thanks to parallel requests since HTTP/2, this can scale to many modules without a performance hit. In production To deploy, all we need is Django's support for collecting static files into one place and its support for adding hashes to filenames. In production it is a good idea to use ManifestStaticFilesStorage storage backend. It stores the file names it handles by appending the MD5 hash of the file’s content to the filename. This allows you to set far future cache expiries, which is good for performance, while still guaranteeing new versions of the file will make it to users’ browsers. This backend is also able to update the reference to form_validation.js in the import statement, with its new versioned file name. Future work ManifestStaticFilesStorage works, but a lot of its implementation details get in the way. It could be easier to use as a developer. The support for import/export with hashed files is not very robust. Comments in CSS with references to files can lead to errors during collectstatic. Circular dependencies in CSS/JS can not be processed. Errors during collectstatic when files are missing are not always clear. Differences between implementation of StaticFilesStorage and ManifestStaticFilesStorage can lead to errors in production that don't show up in development (like #26329, about leading slashes). Configuring common options means subclassing the storage when we could use the existing OPTIONS dict. Collecting static files could be faster if it used parallelization (pull request: #19935 Used a threadpool to parallelise collectstatic) We discussed those possible improvements at the Django on the Med 🏖️ sprints and I’m hopeful we can make progress. I built django-manifeststaticfiles-enhanced to attempt to fix all these. The core work is to switch to a lexer for CSS and JS, based on Ned Batchelder’s JsLex that was used in Django previously. It was expanded to cover modern JS and CSS by working with Claude Code to do the grunt work of covering the syntax. It also switches to using a topological sort to find dependencies, whereas before we used a more brute force approach of repeated processing until we saw no more changes, which lead to more work, particularly on storages that used the network. It also meant we couldn't handle circular dependencies. To validate it works, I ran a performance benchmark on 50+ projects, it’s been tested issues and with similar (often improved) performance. On average, it’s about 30% faster. While those improvements would be welcome, do go ahead with trying build-free JavaScript and CSS in your Django projects today! Modern browsers make it possible to create great frontend experiences without the complexity.

Last week, we had a great time at PyCon FR 2025 - a free (!) gathering for Pythonistas in France. Here are some of our highlights. Sprints on Django, our website, IA, marketing Over two days, the conference started with 27 contributors joining us to contribute to Django and our website and online presence. Half in the room were complete newcomers to open source, wanting to get a taste of what it’s like behind the scenes. We also had people who were new to Django, taking the excellent Django Girls tutorial to get up to speed with the project. The tutorial is translated in 20 languages(!), so it’s excellent in situations like this where people come from all over Europe. Carmen, one of our sprint contributors, took the time to test that our software for ongoing Board elections is accessible 💚 Discussing Django’s direction At the sprints, we also organized discussions on Django’s direction - specifically on marketing, Artificial Intelligence, and technical decisions. Some recurring topics were: Highlights from the State of Django 2025 report produced by JetBrains, and the need for fundraising partnerships like their ongoing 30% Off PyCharm Pro – 100% for Django campaign. What “batteries included” means for Django in 2025. Does it include REST? Contributors discussed the recent forum thread Django needs a REST story. Type hints and Django. The existing feature requests, and how feature requests are meant to work for Django. The impact of Artificial Intelligence on Django and Django developers. How AI adoption could be supported with documentation investments, but also the ethical concerns of AI coding. We had a great time during those two days of sprints ❤️ thank you to everyone involved, we hope you stick around! Design systems with JinjaX, Stimulus, and Cube CSS Mads demonstrated how to bring a design-system mindset to Django projects by combining JinjaX, Stimulus JS, and Cube CSS. Supported by modern tooling like Figma, Vite, and Storybook. JinjaX in particular, allows to take a more component-driven “lego blocks” approach to front-end development with Django. Three years of htmx in Django Céline Martinet Sanchez shared her takeaways from using htmx with Django over three years. The verdict? A joyful developer experience, some (solved) challenges with testing. Her recommended additions to make the most of the two frameworks: django-htmx: opinionated htmx integration Slippers: better DX for Django templates factory_boy: test data generator (alternative to fixtures) Syrupy: snapshots for pytest Becoming an open-source contributor in 2025 In her talk, Amanda Savluchinske explored how newcomers can get involved in open source—highlighting the Django community’s Djangonaut Space program. She explains why doing it is great, how to engage with busy maintainers, and specific actions people can take to get started. We really liked her sharing a prompt she uses with AI, to iterate on questions to maintainers before hitting “send”: “You are an expert in technical writing. I'm trying to write a message about a question I have about this open-source project I'm contributing to. Here's the link to its repo ‹Add link here›. I want to convey my question to the maintainers in a clear, concise way, at the same time that I want it to have enough context so that the communication happens with the least back and forth possible. I want this question to contain a short, max two sentence summary upfront, and then more context in the text's body. Ask me whatever questions you need about my question and context in order to produce this message.” La Suite numérique: government collaboration powered by Django PyCon FR also featured La Suite numérique, the French government’s collaborative workspace—developed with partners in Germany, the Netherlands (Mijn Bureau), and Italy. Their platform includes collaborative documents, video calls, chat, and an AI assistant — all powered by Django 🤘. This work is now part of a wider European Union initiative for sovereign digital infrastructure based on open source, for more information see: Commission to launch Digital Commons EDIC to support sovereign European digital infrastructure and technology. Up next… Up next, we have the first ever Django Day India event! And closer to France, DjangoCon Europe 2026 will take place in Athens, Greece 🇬🇷🏖️🏛️☀️ We’re elated to support events like PyCon FR 2025. To help us do more of this, take a look at this great offer from JetBrains: 30% Off PyCharm Pro – 100% for Django – All money goes to the Django Software Foundation!