Django community: RSS
This page, updated regularly, aggregates Django Software Foundation from the Django community.
-
PyCharm & Django Fundraiser Extended to September 14
The second half of our annual JetBrains fundraiser has been extended through September 14, 2026. Thank you to JetBrains for the extra time. You still have time to renew your PyCharm license or give it a try. You get PyCharm at 30% off, and JetBrains donates 100% of your purchase or renewal to the DSF. This is one of the DSF's bigger fundraisers of the year, and we appreciate everyone who takes a look. The Executive Director search also closes on September 14, and we are curious to see who reaches out. JetBrains has been a steady sponsor for years, and it was great to see the chatter around the Django Developers Survey 2026 results we released with them last month. The full report is on the JetBrains site. If you are shopping for an IDE, AI-focused or not, they have a solid product. If you would like to help with our fundraising goals, we would love to hear from you or your company. The board is happy to talk with individuals too, if you have ideas. Whatever you can do to support us, we appreciate it. Ways to help Renew or start a PyCharm license through the fundraiser before … -
Call for volunteers: Fundraising Working Group
The Django Software Foundation is looking for people to join the Fundraising Working Group. This is a particularly interesting time to get involved. The DSF has raised its 2026 fundraising goal to $500,000. That funding is what allows us to continue supporting the Django Fellows, Django Girls, community events, Djangonaut Space, infrastructure, and the many other things that keep the Django ecosystem going. It also gives the DSF the room to do something new: hire its first Executive Director. You can read more about the DSF's fundraising goals for 2026 in this post. Getting there will take more than asking people to donate. We need to think about how we build relationships with companies that depend on Django, how we make sponsorships meaningful, how we find new ways for organisations to support the project, and how we communicate the value of investing in Django. That is where the Fundraising Working Group comes in. The DSF is hiring an Executive Director who will bring dedicated, day-to-day leadership to the Foundation, including sponsorship development and partner relationships. The Fundraising Working Group will have an opportunity to work closely with the person in this role as we build out our fundraising efforts. Who … -
Django bugfix release issued: 6.1.1
Today we've issued the 6.1.1 bugfix release. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7 -
Djangonaut Space - Session 7 Accepting Applications
We are thrilled to announce that Djangonaut Space, a mentorship program for contributing to Django, is open for applicants for our next cohort! 🚀 Session 7 launches October 12th, 2026. We are currently accepting applications until September 6th, 2026 Anywhere on Earth. More details can be found in the website. Djangonaut Space is a free, 8-week group mentoring program where individuals will work self-paced in a semi-structured learning environment. It seeks to help members of the community who wish to level up their current Django code contributions and potentially take on leadership roles in Django in the future. Rodrigo Vieira, Djangonaut Session 6 “Participating as a mentee in the Djangonaut Space was a highly valuable experience. The program provided clear, step-by-step guidance on how to navigate the core framework, find the right issues to tackle, and confidently send my PRs. Beyond the code, the community on Discord was very active, sharing experiences, wins and support. We had access to regular talks, Django Fellows and long-time maintainers who generously shared their time and expertise. It was a welcoming environment to connect with other newcomers from all over the world, allowing us to share our journeys and learn together. The highlight of … -
DSF member of the month - Benjamin Balder Bach
For August 2026, we welcome Benjamin Balder Bach as our DSF member of the month! ⭐ Benjamin has long been part of the Django community, serving for years as an organizer of Django Day Copenhagen and as Chair of the Social Media Working Group. He is a DSF member since June 2020! You can learn more about Benjamin by visiting Benjamin's website and his GitHub Profile. Let’s spend some time getting to know Benjamin better! Can you tell us a little about yourself? (hobbies, education, etc) Hello! I like DIY in general, so whether it's software, cooking, sewing, growing plants or building stuff with wood - I really like practical things with a finish in sight. I really don't mind when it's not a software project, though 😇 I'll try to nail what my education and work is about: I started as a self-taught programmer when I had a job at 15 (as a web designer). Before that, I had been delivering newspapers and cleaning toilets at my school, so it was a pretty big leap forward. I knew HTML but learned about SQL and ASP classic (not .net) because my employer back in 2000 let me learn while working. … -
Django Developers Survey 2026 results
The results from the 2026 Django Developers Survey are now available. This is the fifth annual report conducted from May to July 2026 by the Django Software Foundation in collaboration with JetBrains PyCharm. The full report includes infographics, quotes, and dedicated sections so you can easily navigate the results. There is also a The State of Django 2026: Boring is so back blog post highlighting key Django trends in 2026 and actionable ideas for your own Django development. The Django Chat podcast also covers the survey in a special summer episode, from Django 6.1 and HTMX to async, AI, deployment, testing, and Python tooling. -
PyCharm & Django Fall Fundraiser
We are back with our friends at JetBrains for the second of the two "Buy PyCharm, Support Django" fundraisers we run together each year. Our spring campaign was the first. It remains one of the most impactful ways the community can support the Django Software Foundation. Your support of this campaign helps fund key initiatives such as: A Django Executive Director: Funding our first Executive Director, who will lead fundraising, operations, and community coordination for the Foundation. Django Fellows: Ensuring the rapid development and maintenance of Django. Django Girls: Making the Django community accessible to programming beginners around the world. International events and conferences: Supporting DjangoCons, one-day events, meetups, and other community gatherings around the world. Djangonaut Space: Onboarding new contributors to the Django project. The Executive Director role is new, which is why this campaign matters more than usual. The DSF raises around $300,000 a year today. Reaching $500,000 is what makes a full-time Executive Director sustainable, and campaigns like this one are how we close that gap. If leading that work sounds like you, applications are open until September 14, 2026. How the campaign works The campaign runs until September 7, 2026. When you buy a new PyCharm … -
The Block and Tackle of Django's Code of Conduct Working Group
In early 2026, Django's Code of Conduct Working Group adopted Contributor Covenant 3.0 as Django's Code of Conduct. I talked about why at DjangoCon US 2026 (slides here). That talk was mostly the story of how we managed the people side of the process. This post is the technical mechanics of how we managed the change and our work going forward. Who can change what, and who has to sign off The Code of Conduct Working Group is established by the DSF board and kept deliberately small. At least three people, per the working group manual, recruited for diversity of geography, background, and lived experience rather than just availability. Membership is volunteer and term-limited. Terms became annual in February 2026, and if a member doesn't respond to the January renewal check-in within a week, they're rolled off. Nobody has to feel guilty about stepping back. The board isn't a separate, distant approval layer sitting above the working group. The DSF board's president always holds a seat on the working group and acts as its board liaison. Other board members can volunteer alongside them, and two currently do, in addition to the chair. Day to day, the working group operates independently. … -
DSF Membership Open Space at DjangoCon US
If you are at DjangoCon US this year, join us for 45 minutes to talk about the Django Software Foundation. What: Django Software Foundation Membership Open Space When: Wednesday, August 26th, 1:00 pm to 1:45 pm Where: Wolf Point Ballroom, voco Chicago Downtown Schedule: Talks: Wednesday, Aug 26 DSF Board Directors Jeff Triplett, Abigail Afi Gbadago, and Paolo Melchiorre will be there, along with Django Fellows, Steering Council members, and other DSF members. This is an open space, not a talk. Pull up a chair and bring your questions. What We Want to Talk About Fundraising and finances. We raised our 2026 goal to $500,000. We'll cover what it funds, most of it the Django Fellows, and how we are tracking against it. If your company depends on Django, or you know one that does, ask us about corporate membership and sponsorship. The Executive Director search. The DSF is hiring its first Executive Director, and applications are open through midnight Central Time on September 14, 2026. If you are thinking about applying, or know someone who should, ask us about the role. Membership. How individual membership works, how people become members, and what members do. Members vote in DSF elections, … -
DSF Office Hours
The DSF Board hosts open office hours every Wednesday at 6:00 PM UTC (check your local time). Anyone in the Django community is welcome to drop in. You do not need an agenda or an invitation. Video call details are on the DSF Office Hours page. We have been running these since October 2024, and right now we have two things we would especially like to talk with you about. Who shows up On any given Wednesday, you might find DSF Board members, Steering Council members, Django Fellows, working group members, and community members who are curious about joining a working group. There is no membership requirement. Anybody from the community can join, and often does. The Executive Director search We recently published a call for applicants for a Django Executive Director. If you are considering applying, or you are still deciding whether it is the right fit, come to office hours and ask us anything: what the job actually looks like, what we expect in the first year, how the search works. We would rather answer your questions directly than have you guess from a job posting. If this is the first you are hearing about the search, please … -
Django is moving to an annual release cycle
Django's Steering Council has accepted the Django Enhancement Proposal DEP 20 to move Django to an annual release cycle. From January 2028, Django will make one feature release a year, giving every feature release the LTS-level three years of support, and version numbers will carry the feature release year: Django 2028, then Django 2029, and so on. Better Python support Python releases annually, each October. Django's eight-month cycle hasn't fit that well: LTS releases carried a wide Python matrix, including versions long past their upstream end-of-life. Under the new cycle, each Django version supports the three latest Python versions at release, and picks up the new Python version during its first year. Django's support window ends in step with its oldest supported Python. Every release is an LTS Every feature release gets three years of support: one year of mainstream bugfixes, then two years of security and data-loss fixes. The "LTS" label is retired — every feature release now carries that same, unique commitment. No more LTS gap: no racing a deadline to jump two years of changes at once. Upgrade one year at a time, whenever suits you within the support window. Three versions are supported at any time, … -
Call for applicants for a Django Executive Director
The Django Software Foundation is announcing a call for an Executive Director. The Executive Director is the operational leader of the Django Software Foundation, a paid position reporting to the Board of Directors, responsible for setting the Foundation's strategic direction and turning it into action, while managing day-to-day operations. They serve as the main connector between the Board, staff, community, and sponsors. The Django Software Foundation (DSF) is a 501(c)(3) nonprofit that develops and maintains Django, a free and open-source web application framework. The Foundation exists to support the development of Django by sponsoring sprints, meetups, gatherings and community events; to promote the use of Django among the web development community; to protect the framework's intellectual property and long-term viability; and to advance the state of the art in web development. This is a new role for the Foundation. Django itself has been around since 2005, but the DSF wasn't founded until 2008, and the person who takes on this role will play a key part in maturing the Foundation's internal structure, helping ensure the DSF can properly support and sustain this important ecosystem going forward. The position is initially for a period of one year, renewable subject to an … -
Django 6.1 released
The Django team is happy to announce the release of Django 6.1. The release notes offer a harmonious mélange of new features and usability improvements. A few highlights are: Model field fetch modes for configuring on-demand fetching behavior Database-level delete options for ForeignKey.on_delete Dictionary-based email settings You can get Django 6.1 from our downloads page or from the Python Package Index. The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7 With the release of Django 6.1, Django 6.0 has reached the end of mainstream support. The final minor bug fix release, 6.0.8, which was also a security release, was issued yesterday, Aug. 4, 2026. Django 6.0 will receive security and data loss fixes until April 2027. All users are encouraged to upgrade before then to continue receiving fixes for security issues. See the downloads page for a table of supported versions and the future release schedule. -
Django security releases issued: 6.0.8 and 5.2.17
In accordance with our security release policy, the Django team is issuing releases for Django 6.0.8 and Django 5.2.17. These releases address the security issues detailed below. We encourage all users of Django to upgrade as soon as possible. CVE-2026-15307: Server-side file-write and request forgery via spatial lookups Spatial lookups allowed str and dict lookup values to be passed to GDALRaster when they represented rasters. Depending on the raster driver, this could write a file to disk (in some cases enabling remote code execution) or issue a network request as the Django process user. Because the admin changelist permits filtering via ModelAdmin.lookup_allowed(), the flaw was reachable by staff users with view permissions on any registered model containing a spatial field. The following types are now disallowed by spatial lookups: dict A str that is not a valid GEOSGeometry, e.g. a serialized dictionary This is a backward incompatible change. As a reminder, all untrusted user input should be validated before use. For that reason, assignments to model fields are unaffected and still accept these input types. For guidance on how to keep using these types in spatial lookups, on validating untrusted input, and on further security considerations, see the raster security … -
DSF member of the month - Katherine "Kati" Michel
For July 2026, we welcome Katherine "Kati" Michel as our DSF member of the month! ⭐ Kati is involved in the Django community for many years. She was a DEFNA Director for 8 years and DjangoCon US Website Chair and Co-Chair. She is a DSF member since December 2017! You can learn more about Kati by visiting Kati's website and her GitHub Profile. Let’s spend some time getting to know Kati better! Can you tell us a little about yourself? (hobbies, education, etc) In 2002, I was living in Lawrence, Kansas and working for government contracts supporting US Citizenship and Immigration Services and the US Department of Education. While working for USCIS, I spoke to tens of thousands of people from around the world, but hadn't seen much of the world myself. In 2009, I decided to move to England and earn a master's degree from Lancaster University Management School. During the program, I was fortunate to have an internship in the IT Change Management Department of Co-operative Financial Services/Britannia Building Society. It feels full circle that I am now a software engineer at JPMorganChase, working in Infrastructure Platforms, Databases Department. How did you start using Django? While living in … -
See You in Chicago in One Month!
In just one month, developers, maintainers, educators, and Django enthusiasts from around the world will gather in Chicago for DjangoCon US 2026. DjangoCon US is more than a conference, it's a place to learn from the community, share ideas, contribute to Django, and make connections that last long after the event ends. Whether you're attending your first DjangoCon US or you've been coming for years, we're excited to welcome you. Over five days, attendees will have the opportunity to: Learn from expert speakers and community members Participate in hands-on tutorials Collaborate during Django sprints Join Open Spaces and informal discussions Meet fellow Django developers from across the globe If you're planning to join us, tickets are still available, and there's still time to reserve your stay at the conference hotel. The hotel room block deadline is August 3, so be sure to book your room before then. Register today! August 24–28, 2026 Chicago, Illinois We can't wait to see you in Chicago! -
Django 6.1 release candidate 1 released
Django 6.1 release candidate 1 is now available. It represents the final opportunity for you to try out the version that offers a harmonious mélange of new features and usability improvements, before Django 6.1 final 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.1 will be released on or around August 5. Any delays will be communicated 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 Jacob Walls: 131403F4D16D8DC7 -
Supporting the Triptych Project
The Django Steering Council — in its role as the DSF's arm for technical governance — has provided a Letter of Collaboration in support of a funding application by Carson Gross and Alex Petros to advance the Triptych Project: three proposals to make HTML itself more expressive, in every browser, by default. Here's why, and how you can help. HTML over the wire, and Django The last few years have seen a move back towards serving multipage applications, with server-rendered templates. The HTMX library has probably had the biggest impact in the Django space, but Unpoly, Turbo, and others are part of the same story: send HTML over the wire, let the browser do what browsers do, and skip the client-side application layer where you don't really need it. It's a simpler model of the web — and it's one that speaks to Django's heart. This isn't a movement Django has watched from the sidelines. Template partials, added in Django 6.0, were directly inspired by the patterns these libraries make natural. The Triptych Project The Triptych Project takes the core insights from HTMX (and the related libraries) and proposes them for the HTML standard itself. Three small additions: PUT, PATCH, … -
Explore the DjangoCon US 2026 Speaker Lineup and Reserve Your Spot
DjangoCon US 2026 is just around the corner, and now is the perfect time to start planning your conference experience. Our speaker lineup is now available, featuring talks from Django contributors, maintainers, educators, and community members covering everything from web development and APIs to deployment, security, testing, AI, and the future of the Django ecosystem. Whether you're attending your first DjangoCon US or returning to reconnect with friends and colleagues, you'll find opportunities to learn, share ideas, and meet people from across the global Django community. Beyond the talks, your conference registration includes access to tutorials, Open Spaces, community sprints, hallway conversations, and social events that make DjangoCon US a unique experience. If you haven't registered yet, there's still time to join us in Chicago, August 24–28. Register for DjangoCon US 2026: https://2026.djangocon.us Browse the speaker lineup: https://2026.djangocon.us/news/announcing-lineup/ We'll be sharing more updates in the coming weeks, including the full conference schedule, travel reminders, and everything you need to make the most of your time at DjangoCon US. We look forward to seeing you in Chicago this August! -
Last Call 2026 Django Developer Survey
Time is running out. This is the last call for the 2026 Django Developers Survey, which the Django Software Foundation is running in partnership with JetBrains. The survey closes on July 13, 2026. It is one of the best measures we have of how Django is used, and it helps guide future technical and community decisions. So far, over 3,100 people have responded, and we would love to push that number past 4,000. Every response helps us better understand the Django community. This year's survey was shaped by the Django Steering Council, the Django Fellows, the Django Software Foundation Board of Directors, and several community members. Your feedback helps us understand your needs, see how you use Django, and plan for future development and community needs. How you can help Once you’ve done the survey, take a moment to re-share on socials and with your communities. The more diverse the answers, the better the results for all of us. We appreciate everybody helping to get the word out. Please use the following links: Bluesky https://surveys.jetbrains.com/s3/bs-django-developers-survey-2026 Django Forum https://surveys.jetbrains.com/s3/df-django-developers-survey-2026 LinkedIn https://surveys.jetbrains.com/s3/li-django-developers-survey-2026 Mastodon https://surveys.jetbrains.com/s3/md-django-developers-survey-2026 Reddit https://surveys.jetbrains.com/s3/r-django-developers-survey-2026 X / Twitter https://surveys.jetbrains.com/s3/x-django-developers-survey-2026 For more details, read the original announcement on the Django blog. -
Django security releases issued: 6.0.7 and 5.2.16
In accordance with our security release policy, the Django team is issuing releases for Django 6.0.7 and Django 5.2.16. These releases address the security issues detailed below. We encourage all users of Django to upgrade as soon as possible. CVE-2026-48588: Potential exposure of private data via cached Set-Cookie response django.middleware.cache.UpdateCacheMiddleware and django.views.decorators.cache.cache_page avoided caching responses that set a cookie while varying on Cookie only when the incoming request contained no cookies at all. When the request already carried an unrelated cookie (such as a language or theme preference cookie), the protection did not apply, allowing a response that sets a session or other sensitive cookie to be stored in Django's shared cache. This issue has severity "low" according to the Django security policy. Thanks to Chris Whyland for the report. CVE-2026-53877: Heap buffer over-read in GDALRaster When django.contrib.gis.gdal.GDALRaster was instantiated with a bytes object representing a raster file, the vsi_buffer property could over-read the allocated buffer by approximately 32 bytes. This could result in information disclosure of adjacent heap memory or, in rare cases, a segmentation fault. Only rasters stored in GDAL's virtual filesystem were affected. This issue has severity "low" according to the Django security policy. Thanks to Bence … -
Keeping Up with the Django Community
The Django community runs on volunteer effort spread across several different groups of people. Most of it is public, but it isn't always easy to find. Here are the public places to find it: Weekly DSF Office Hours (website) DSF Board updates (website, GitHub repo) Steering Council (forum thread, GitHub repo) Website Working Group (forum thread) Online Community Working Group (forum thread) Django Fellow Reports (Jacob, Natalia, Sarah) DSF Office Hours Most of these are places to read and follow along, but one invites you to show up in real time, the DSF Office Hours. From the website: These are weekly office hours to work on anything related to the DSF. At least one board member will try to attend each week. Office hours take place every Wednesday at 6:00 PM UTC. All you need to do is bring something DSF-related to work on. This is intentionally broad, as long as it's vaguely DSF-related you're welcome to come. It's not a general-purpose Django coding session (you're welcome to be writing code but it should be related the DSF, e.g. working on djangoproject.com or something). They are friendly and casual. People are welcome to bring topics and discussions for everyone to … -
DSF member of the month - Salim Nuru
For June 2026, we welcome Salim Nuru as our DSF member of the month! ⭐ Salim was a Djangonaut Space participant in the first session. He has been an organiser of the DjangoCon Africa conference. He is currently the chair of the DjangoCon US website. He a DSF member since October 2024. He is looking for new opportunities! You can learn more about Salim by visiting Salim's blog and his GitHub Profile. Let’s spend some time getting to know Salim better! Can you tell us a little about yourself (hobbies, education, etc)? I'm Salim, I’m from Addis, Ababa Ethiopia. I'm a software engineer by day and a security researcher by night. And for fun, I like chess, video games, and books. I already have an idea, but where does your nickname "theShinigami" come from? I LOVE anime, and the very first anime I watched was Death Note. There's this character called Ryuk, who is a "shinigami," and when I created my GitHub account, it was a time when I was really into anime (which I still am). That's why it stuck as my GitHub username. How did you start using Django? I started using Django during my college years. I … -
How the Django Software Foundation Became a CNA
Why the DSF pursued CNA status Django has a long history of responsible security practices: a dedicated, private security mailing list, clear advisory policies, and predictable security releases. Even so, we relied on external organizations to assign CVE IDs (Common Vulnerabilities and Exposures). This sometimes introduced administrative delays and extra coordination overhead. Becoming a CNA (CVE Numbering Authority) allows the DSF to: Assign CVEs ourselves for vulnerabilities in Django and selected community projects. Publish advisories more efficiently and in closer alignment with Django's established release workflow. Maintain strong independence in how Django handles security incidents. The initial exploration The process began with internal discussions within the DSF Board and Django Security Team. We evaluated: Whether our existing security process already met CNA expectations. Whether we had the organizational stability to take on long term responsibility for CVE assignment. The scope of projects we would cover. How to ensure we could meet the operational requirements without overloading volunteers and Django Fellows. After confirming that our policies were mature and that the administrative workload would be manageable, we initiated the CNA application with MITRE. Preparing the application MITRE requires that new CNAs document their security processes and demonstrate that they can meet … -
Django 6.1 beta 1 released
Django 6.1 beta 1 is now available. It represents the second stage in the 6.1 release cycle and is an opportunity to try out the changes coming in Django 6.1. Django 6.1 offers a harmonious mélange of new features and usability improvements, which you can read about in the in-development 6.1 release notes. Only bugs in new features and regressions from earlier Django versions will be fixed between now and the 6.1 final release. Translations will be updated following the "string freeze", which occurs when the release candidate is issued. The current release schedule calls for a release candidate in about a month, with the final release scheduled roughly two weeks later on August 5. Early and frequent testing from the community will help minimize the number of bugs in the release. Updates on the release schedule are available on the Django forum. As with all alpha and beta packages, this release is not for production use. However, if you'd like to try some of the new features or help find and fix bugs (which should be reported to the issue tracker), you can grab a copy of the beta package from our downloads page or on PyPI. The PGP …
