For April 2026, we welcome Rob Hudson as our DSF member of the month! ⭐ Rob is the creator of django-debug-toolbar (DDT), tool used by more than 100 000 folks in the world. He introduces Content-Security-Policy (CSP) support in Django and contribute to many open source packages. He has been a DSF member since February 2024. You can learn more about Rob by visiting Rob's website and his GitHub Profile. Let’s spend some time getting to know Rob better! Can you tell us a little about yourself I'm a backend Python engineer based in Oregon, USA. I studied biochemistry in college, where software was just a curiosity and hobby on the side, but I'm grateful that my curiosity turned into a career in tech. My earliest memory of that curiosity was taking apart my Speak & Spell as a kid to see how it worked and never quite getting it back together again. How did you start using Django? I followed the path of the "P"s: Perl, then PHP, then Python. When Ruby on Rails arrived it was getting a lot of attention, but I was already enjoying Python, so when Django was announced I was immediately drawn to it. I started building small apps on my own, then eventually led a broader tech stack modernization at work, a health education company where we were building database-driven learning experiences with quizzes and a choose-your-own-adventure flow through health content. Django, Git, and GitHub all came together around that same time as part of that transition. Fun fact: my GitHub user ID is 1106. 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 been building a few projects with FastAPI lately and have really come to appreciate the type-based approach to validation via Pydantic. The way typing syntax influences the validation logic is something I'd love to see influence Django more over time. Erlang has a feature called the crash dump: when something goes wrong, the runtime writes out the full state of every process to a file you can open and inspect after the fact. As someone who built a debug toolbar because I wanted to see what was going on under the hood. Being provided a freeze frame of the exact moment things went wrong, full state intact, ready to inspect sounds like magic. The Rust-based tooling emerging in the Python ecosystem is fascinating to watch. Tools like uv, ruff, and efforts around template engines, JSON encoders, ASGI servers, etc. The potential for significant speed improvements without losing what makes Django Django is an interesting space. What projects are you working on now? I have a couple of personal fintech projects I'm playing with, one using FastAPI and one using Django. I've been enjoying exploring and wiring up django-bolt for the Django project. I'm impressed with the speed and developer friendliness. On the django-debug-toolbar front, I recently contributed a cache storage backend and have a longer term idea to add an API layer and a TUI interface that I'd love to get back to working on someday. Which Django libraries are your favorite (core or 3rd party)? Django Debug Toolbar (I may be slightly biased). Beyond that: whitenoise and dj-database-url are great examples of libraries that do one thing well and get out of your way. I'd also add granian, a Rust-based ASGI server. And django-allauth, which I'm somehow only just trying for the first time. For settings management I've cycled through a few libraries over the years and am currently eyeing pydantic-settings for a 12-factor approach to configuration. What are the top three things in Django that you like? The community. I've been part of it for a long time and it has a quality that's hard to put into words. It feels close knit, genuinely welcoming to newcomers, and there's a rising tide lifts all boats mentality that I don't think you find everywhere. People care about helping each other succeed. The sprints and hallway track at DjangoCon have been a wonderful extension of that. The ORM. Coming from writing a lot of raw SQL, I appreciate the syntax of Django's ORM which hits a sweet spot of simplicity and power for most use cases. Stability, documentation, and the batteries included philosophy. I appreciate a framework that at its core doesn't chase trends, has a predictable release cycle, amazingly well written docs (which makes sense coming from its journalism background), and there's enough built in to get surprisingly far without reaching for third party packages. You are the creator of Django Debug Toolbar, this tool is really popular! What made you create the tool and publish the package? The inspiration came from Symfony, a PHP framework that had a debug toolbar built in. At the time, I was evaluating frameworks for a tech stack transition at work and thought, why doesn't Django have one of these? So I started hacking on a simple middleware that collected basic stats and SQL queries and injected the toolbar HTML into the rendered page. The first commit was August 2008. The SQL piece was personally important. Coming from PHP where I wrote a lot of raw SQL by hand, I wanted to see what the ORM was actually generating. The nudge to actually release it came at the first DjangoCon in 2008 at Google's headquarters. Cal Henderson gave a keynote called "Why I Hate Django" and showed a screenshot of Pownce's debug toolbar in the page header, then talked about internal tooling at Flickr similar to what the Django debug toolbar has currently. Seeing those motivated me to tweet out what I was working on that same day. Apparently I wasn't the only one who wanted to see what the ORM was doing. It has been created in 2008, what are your reflections on it after so many years? Mostly gratitude. I had a young family at the time and life got busy, so I stepped back from active maintenance earlier than I would have liked. Watching it flourish under the maintainers who stepped up has been really wonderful to see. They've improved it, kept up with releases, supported the community, and have done a better job of it than I was in a position to do at the time, so I'm grateful to all who carried the torch. At this point I contribute to it like any other project, which might sound strange for something I created, but it's grown bigger than my early involvement and that feels right. I still follow along and it makes me happy to see it continuing to grow and evolve. What I didn't anticipate was what it gave back. It helped launch my career as a Django backend developer and I'm fairly certain it played a role in landing me a job at Mozilla. All from of a middleware I hacked together just to see what the ORM was doing. Being a maintainer is not always easy despite the fact it can be really amazing. Do you have any advice for current and future maintainers in open source? For what it's worth, what worked for me was building things for fun and to learn rather than setting out to build something popular. I also didn't worry too much about perfection or polish early on. If life gets busy or your interests move on, I'd say trust the community. Have fun, and if it stops being fun, find some enthusiastic people who still think it's fun and hand it to them gracefully. That worked out better than I could have hoped in my case. I'm genuinely curious about how AI changes open source. If simple utilities can be generated on the fly rather than installed as packages, what does that mean for small focused libraries? My hope is that the value of open source was never just the code anyway. The collaboration, the issue discussions, the relationships. AI can generate code but it can't replicate those things. One thing I've noticed is newer developers using AI to generate patches they don't fully understand and submitting them as contributions. I get the impulse, but I'd encourage using AI as a tool for curiosity rather than a shortcut. Let it suggest a fix, then dig into why it works, ask it questions, iterate, which is something I often do myself. You have introduced CSP support in Django core, congratulations and thank you for this addition! How did the process of creating this contribution go for you? I picked up django-csp at Mozilla because it had become unmaintained and was a blocker from upgrading to newer Python and Django versions. What started as a simple maintenance task turned into a bit of a yak shave, but a good one. Getting up to speed on CSP led to ticket triage, which led to a refactor, which eventually led me to a 14 year old Django issue requesting CSP in core. Once the refactor was done I made the mistake of actually reading that 14 year old ticket and then felt personally responsible for it. The more I worked in the space the clearer the ecosystem problem became. As a third party package, django-csp couldn't provide a standardized API that other packages could reliably depend on. If a third party library needed to add nonces to their own templates, they couldn't assume django-csp was installed. Seeing that friction play out in projects like debug toolbar and Wagtail convinced me that CSP support made sense in core. Working with the Django fellows through the process was a genuine pleasure and I have enormous respect for what they do. They are patient, kind, and shaped what landed in core immensely. What surprised me most was how much they handle behind the scenes and how gracefully they manage the constant demands on their attention. Huge props to Natalia in particular for guiding a large and complex feature through to completion. Do you remember your first contribution to open source? Before Django I'd been tinkering on the web for years. I built tastybrew, an online homebrew recipe calculator and sharing site, partly to scratch my own itch and partly to get deeper with PHP and hosting my own projects. Back then open source collaboration wasn't what it is today. Before GitHub there was Freshmeat, SourceForge, emailed patches, maybe your own server with a tarball to download. My first Django contribution was a small fix to the password reset view in 2006. Over the next several years there were around 40 or so contributions like docs corrections, admin improvements, email handling, security fixes. Contributing felt natural because the code was open and the community was welcoming. I joined Mozilla in 2011 and shifted focus for a while. Mozilla was quietly contributing quite a bit back to the Django ecosystem during those years, with many 3rd party Django libraries, like django-csp. One of my favorite open source contributions was when I collaborated with a colleague on a Python DSL for Elasticsearch that eventually became the basis for Elastic's official Python client. What are your hobbies or what do you do when you’re not working? Reading, cooking, and getting outside when I can. I try to eat a whole food plant based diet and enjoy cooking in that style. Not sure it counts as a hobby but I enjoy wandering grocery stores, browsing what's new, reading ingredients, curious about flavors, thinking about what I could recreate at home. Getting away from screens is important to me. Gardening, hiking, camping, long walks, travel when possible. Petrichor after rain. Puzzles while listening to audiobooks or podcasts. I brew oolong tea every day, a quiet ritual where the only notification is my tea timer. Code has always felt more like curiosity than work to me, so I'm not sure where hobby ends and the rest begins. Anything else you'd like to share? If you have a Django codebase that needs some love, I'm available for contract work. I genuinely enjoy the unglamorous stuff: upgrading legacy codebases, adding CSP support, and refactoring for simplicity and long term maintainability. There's something satisfying about stepping back, seeing the bigger picture, and leaving things cleaner than you found them. You can find me on GitHub at robhudson. Doing this interview was a nice way to reflect on my career. I can see that curiosity and adaptation have been pretty good companions. I'm grateful Django and its community have been a big part of that journey. Thank you for doing the interview, Rob !

Hello Django community, The Steering Council is excited to share our proposed new technical governance and ask for your feedback. Last year we suspended the formal voting process of the Steering Council. The updates we’re proposing would bring how we’ve been operating into alignment with the written governance. From the motivation section: This is a revisitation of Django's technical governance in which a simplification and reduction was made to make it more approachable to more people. The goals of these changes are the following: Make it easier to enact our governance. Make it easier for others to understand our governance. Make the governance more flexible, allowing more action with less procedure. You can read DEP 0019 here. Adoption plan The goal is to have this governance accepted and in place by 2026-07-01. Our timeline is as follows, but may change depending on feedback. 2026-04-16: Announce new technical governance, solicit feedback 2026-05-07: Merge in minor feedback changes 2026-05-28: Resolve major feedback concerns 2026-06-11: Steering Council and DSF Board vote on and approve DEP What we need from you We would like to know if we are achieving our goals with this document. For example, do you feel that this makes our governance easier to understand, do you feel like you have a better understanding of who is eligible to run for the Steering Council, is it clear how Django operates from a process perspective? Beyond that, if you have other feedback around the changes, please share it. This has gone through a high degree of review from the Steering Council and Board over the past 5 months, but that doesn’t mean there aren't areas where it can be improved. Anyone can participate in this process on the Forum thread here.

For another year, we are thrilled to partner with our friends at JetBrains on the annual "Buy PyCharm, Support Django" campaign. This is the first of two fundraisers we're running with JetBrains this year, and it's one of the most impactful ways the community can support the Django Software Foundation. "JetBrains is a cornerstone in the Django community, consistently helping us understand our evolving landscape. Their annual survey provides invaluable insights into the community's needs, trends, and tools, ensuring we stay on the pulse of what matters most." Jeff Triplett, President, Django Software Foundation Your support of this campaign helps fund key initiatives such as: Django Fellows: Ensuring the rapid development and maintenance of Django. Djangonaut Space: Onboarding new contributors to the Django project. 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. How the campaign works From today to May 1, when you purchase PyCharm at a 30% discount through our special campaign link, JetBrains will donate an equal amount to the Django Software Foundation. You get a professional IDE that's trusted by Django developers worldwide, and the DSF receives a matched contribution. Get 30% off PyCharm, Support Django Thank you, JetBrains Beyond this campaign, JetBrains contributes to the Django ecosystem in ways that are easy to overlook but hard to overstate. Their Django Developers Survey, State of Django report, and broader Python Developers Survey give the entire community a clearer picture of where Django and Python are heading each year. "JetBrains is one of our most generous fundraising partners year after year, helping us sustain and grow the Django ecosystem. We deeply appreciate their commitment, leadership, and collaboration." Thank you to JetBrains for another year of partnership, and thank you to everyone who participates in this campaign. Together, we can ensure the continued success and growth of the framework we all rely on. Other ways to donate If you would like to donate in another way, especially if you are already a PyCharm customer, here are other ways to donate to the DSF: On our website via credit card Via GitHub Sponsors Benevity Workplace Giving Program - If your employer participates, you can make donations to the DSF via payroll deduction. For those able to make a larger donation as corporate sponsors ($2000+), check out our corporate sponsors form

We’re excited to announce that Django has officially adopted Contributor Covenant 3 as our new Code of Conduct! This milestone represents the completion of a careful, community-driven process that began earlier this year. What We’ve Accomplished Back in February, we announced our plan to adopt Contributor Covenant 3 through a transparent, multi-step process. Today, we’re proud to share that we’ve completed all three steps: Step 1 (Completed February 2026): Established a community-driven process for proposing and reviewing changes to our Code of Conduct. Step 2 (Completed March 2026): Updated our Enforcement Manual, Reporting Guidelines, and FAQs to align with Contributor Covenant 3 and incorporate lessons learned from our working group’s experience. Step 3 (Completed April 2026): Adopted the Contributor Covenant 3 with Django-specific enhancements. Why Contributor Covenant 3? Contributor Covenant 3 represents a significant evolution in community standards, incorporating years of experience from communities around the world. The new version: Centers impact over intent, recognizing that even unintentional harm requires accountability and repair Emphasizes consent and boundaries, making explicit that community members must respect stated boundaries immediately Addresses modern harassment patterns like sea-lioning, coordinated harassment, and microaggressions Includes clearer guidance on enforcement, transparency, and accountability By adopting this widely-used standard, Django joins a global community of projects committed to fostering welcoming, inclusive spaces for everyone. What’s New in Django’s Code of Conduct While we’ve adopted Contributor Covenant 3 as our foundation, we’ve also made Django-specific enhancements: In-person event guidance: Added requirements and best practices for Code of Conduct points of contact at Django events Affiliated programs documentation: Clarified scope and expectations for programs that reference Django’s Code of Conduct Bad-faith reporting provisions: Added protections against misuse of the reporting process Escalation processes: Established clear procedures for handling disagreements between working groups Enhanced transparency: Updated our statistics and reporting to provide better visibility into how we enforce our Code of Conduct You can view the complete changelog of changes at our Code of Conduct repository. Community-Driven Process This adoption represents months of collaborative work. The Code of Conduct Working Group reviewed community feedback, consulted with the DSF Board, and incorporated insights from our enforcement experience. Each step was completed through pull requests that were open for community review and discussion. We’re grateful to everyone who participated in this process—whether by opening issues, commenting on pull requests, joining forum discussions, or simply taking the time to review and understand the changes. Where to Find Everything All of our Code of Conduct documentation is available on both djangoproject.com and our GitHub repository: Code of Conduct: djangoproject.com/conduct Reporting Guidelines: djangoproject.com/conduct/reporting Enforcement Manual: djangoproject.com/conduct/enforcement-manual FAQs: djangoproject.com/conduct/faq GitHub Repository: github.com/django/code-of-conduct How You Can Continue to Help The Code of Conduct is a living document that will continue to evolve with our community’s needs: Propose changes: Anyone can open an issue to suggest improvements Join discussions: Participate in community conversations on the Django forum, Discord, or DSF Slack Report violations: If you experience or witness a Code of Conduct violation, please report it to conduct@djangoproject.com Stay informed: Watch the Code of Conduct repository for updates Thank You Creating a truly welcoming and inclusive community is ongoing work that requires participation from all of us. Thank you for being part of Django’s community and for your commitment to making it a safe, respectful space where everyone can contribute and thrive. If you have questions about the new Code of Conduct or our processes, please don’t hesitate to reach out to the Code of Conduct Working Group at conduct@djangoproject.com. Posted by Dan Ryan on behalf of the Django Code of Conduct Working Group

In accordance with our security release policy, the Django team is issuing releases for Django 6.0.4, Django 5.2.13, and Django 4.2.30. These releases address the security issues detailed below. We encourage all users of Django to upgrade as soon as possible. Django 4.2 has reached the end of extended support Note that with this release, Django 4.2 has reached the end of extended support. All Django 4.2 users are encouraged to upgrade to Django 5.2 or later to continue receiving fixes for security issues. See the downloads page for a table of supported versions and the future release schedule. CVE-2026-3902: ASGI header spoofing via underscore/hyphen conflation ASGIRequest normalizes header names following WSGI conventions, mapping hyphens to underscores. As a result, even in configurations where reverse proxies carefully strip security-sensitive headers named with hyphens, such a header could be spoofed by supplying a header named with underscores. Under WSGI, it is the responsibility of the server or proxy to avoid ambiguous mappings. (Django's runserver was patched in CVE-2015-0219.) But under ASGI, there is not the same uniform expectation, even if many proxies protect against this under default configuration (including nginx via underscores_in_headers off;). Headers containing underscores are now ignored by ASGIRequest, matching the behavior of Daphne, the reference server for ASGI. This issue has severity "low" according to the Django Security Policy. Thanks to Tarek Nakkouch for the report. CVE-2026-4277: Privilege abuse in GenericInlineModelAdmin Add permissions on inline model instances were not validated on submission of forged POST data in GenericInlineModelAdmin. This issue has severity "low" according to the Django Security Policy. Thanks to N05ec@LZU-DSLab for the report. CVE-2026-4292: Privilege abuse in ModelAdmin.list_editable Admin changelist forms using ModelAdmin.list_editable incorrectly allowed new instances to be created via forged POST data. This issue has severity "low" according to the Django Security Policy. CVE-2026-33033: Potential denial-of-service vulnerability in MultiPartParser via base64-encoded file upload When using django.http.multipartparser.MultiPartParser, multipart uploads with Content-Transfer-Encoding: base64 that include excessive whitespace may trigger repeated memory copying, potentially degrading performance. This issue has severity "moderate" according to the Django Security Policy. Thanks to Seokchan Yoon for the report. CVE-2026-33034: Potential denial-of-service vulnerability in ASGI requests via memory upload limit bypass ASGI requests with a missing or understated Content-Length header could bypass the DATA_UPLOAD_MAX_MEMORY_SIZE limit when reading HttpRequest.body, potentially loading an unbounded request body into memory and causing service degradation. This issue has severity "low" according to the Django Security Policy. Thanks to Superior for the report. Affected supported versions Django main Django 6.0 Django 5.2 Django 4.2 Resolution Patches to resolve the issue have been applied to Django's main, 6.0, 5.2, and 4.2 branches. The patches may be obtained from the following changesets. CVE-2026-3902: ASGI header spoofing via underscore/hyphen conflation On the main branch On the 6.0 branch On the 5.2 branch On the 4.2 branch CVE-2026-4277: Privilege abuse in GenericInlineModelAdmin On the main branch On the 6.0 branch On the 5.2 branch On the 4.2 branch CVE-2026-4292: Privilege abuse in ModelAdmin.list_editable On the main branch On the 6.0 branch On the 5.2 branch On the 4.2 branch CVE-2026-33033: Potential denial-of-service vulnerability in MultiPartParser via base64-encoded file upload On the main branch On the 6.0 branch On the 5.2 branch On the 4.2 branch CVE-2026-33034: Potential denial-of-service vulnerability in ASGI requests via memory upload limit bypass On the main branch On the 6.0 branch On the 5.2 branch On the 4.2 branch The following releases have been issued Django 6.0.4 (download Django 6.0.4 | 6.0.4 checksums) Django 5.2.13 (download Django 5.2.13 | 5.2.13 checksums) Django 4.2.30 (download Django 4.2.30 | 4.2.30 checksums) The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7 General notes regarding security reporting As always, we ask that potential security issues be reported via private email to security@djangoproject.com, and not via Django's Trac instance, nor via the Django Forum. Please see our security policies for further information.

We are looking for the next group of organizers to own and lead the 2027 DjangoCon Europe conference. Could your town's football stadium, theatre, cinema, city hall, circus tent or a private island host this wonderful community event? DjangoCon Europe is a major pillar of the Django community, as people from across the world meet and share. Many qualities make it a unique event: Unconventional and conventional venues, creative happenings, a feast of talks and a dedication to inclusion and diversity. Hosting a DjangoCon is an ambitious undertaking. It's hard work, but each year it has been successfully run by a team of community volunteers, not all of whom have had previous experience - more important is enthusiasm, organizational skills, the ability to plan and manage budgets, time and people - and plenty of time to invest in the project. For 2027, rest assured that we will be there to answer questions and put you in touch with previous organizers through the brand new DSF Events Support Working Group (a reboot of the previous DjangoCon Europe Support Working Group). Step 1: Submit your expression of interest If you're considering organizing DjangoCon Europe (🙌 great!), fill in our DjangoCon Europe 2027 expression of interest form with your contact details. No need to fill in all the information at this stage if you don't have it all already, we'll reach out and help you figure it out. Express your interest in organizing Step 2: We're here to help! We've set up a DjangoCon Europe support working group of previous organizers that you can reach out to with questions about organizing and running a DjangoCon Europe. The group will be in touch with everyone submitting the expression of interest form, or you can reach out to them directly: events-support@djangoproject.com We'd love to hear from you as soon as possible, so your proposal can be finalized and sent to the DSF board by June 1st 2026. Step 3: Submitting the proposal The more detailed and complete your final proposal is, the better. Basic details include: Organizing committee members: You won't have a full team yet, probably, naming just some core team members is enough. The legal entity that is intended to run the conference: Even if the entity does not exist yet, please share how you are planning to set it up. Dates: See "What dates are possible in 2027?" below. We must avoid conflicts with major holidays, EuroPython, DjangoCon US, and PyCon US. Venue(s), including size, number of possible attendees, pictures, accessibility concerns, catering, etc. Transport links and accommodation: Can your venue be reached by international travelers? Budgets and ticket prices: Talk to the DjangoCon Europe Support group to get help with this, including information on past event budgets. We also like to see: Timelines Pictures Plans for online participation, and other ways to make the event more inclusive and reduce its environmental footprint Draft agreements with providers Alternatives you have considered Have a look at our proposed (draft, feedback welcome) DjangoCon Europe 2027 Licensing Agreement for the fine print on contractual requirements and involvement of the Django Software Foundation. Submit your completed proposal by June 1st 2026 via our DjangoCon Europe 2027 expression of interest form, this time filling in as many fields as possible. We look forward to reviewing great proposals that continue the excellence the whole community associates with DjangoCon Europe. Q&A Can I organize a conference alone? We strongly recommend that a team of people submit an application. I/we don't have a legal entity yet, is that a problem? Depending on your jurisdiction, this is usually not a problem. But please share your plans about the entity you will use or form in your application. Do I/we need experience with organizing conferences? The support group is here to help you succeed. From experience, we know that many core groups of 2-3 people have been able to run a DjangoCon with guidance from previous organizers and help from volunteers. What is required in order to announce an event? Ultimately, a contract with the venue confirming the dates is crucial, since announcing a conference makes people book calendars, holidays, buy transportation and accommodation etc. This, however, would only be relevant after the DSF board has concluded the application process. Naturally, the application itself cannot contain any guarantees, but it's good to check concrete dates with your venues to ensure they are actually open and currently available, before suggesting these dates in the application. Do we have to do everything ourselves? No. You will definitely be offered lots of help by the community. Typically, conference organizers will divide responsibilities into different teams, making it possible for more volunteers to join. Local organizers are free to choose which areas they want to invite the community to help out with, and a call will go out through a blog post announcement on djangoproject.com and social media. What kind of support can we expect from the Django Software Foundation? The DSF regularly provides grant funding to DjangoCon organizers, to the extent of $6,000 in recent editions. We also offer support via specific working groups: The dedicated DjangoCon Europe support working group. The social media working group can help you promote the event. The Code of Conduct working group works with all event organizers. In addition, a lot of Individual Members of the DSF regularly volunteer at community events. If your team aren't Individual Members, we can reach out to them on your behalf to find volunteers. What dates are possible in 2027? For 2027, DjangoCon Europe should happen between January 4th and April 26th, or June 3rd and June 27th. This is to avoid the following community events' provisional dates: PyCon US 2027: May 2027 EuroPython 2027: July 2027 DjangoCon US 2027: September - October 2027 DjangoCon Africa 2027: August - September 2027 We also want to avoid the following holidays: New Year's Day: Friday 1st January 2027 Chinese New Year: Saturday 6th February 2027 Eid Al-Fitr: Tuesday 9th March 2027 Easter: Sunday 28th March 2027 Passover: Wednesday 21st - Thursday 29th April 2027 Eid Al-Adha: Monday 17th - Thursday 20th May 2027 Rosh Hashanah: Saturday 2nd - Monday 4th October 2027 Yom Kippur: Monday 11th - Tuesday 12th October 2027 What cities or countries are possible? Any city in Europe. This can be a city or country where DjangoCon Europe has happened in the past (Athens, Vigo, Edinburgh, Porto, Copenhagen, Heidelberg, Florence, Budapest, Cardiff, Toulon, Warsaw, Zurich, Amsterdam, Berlin), or a new locale. References Past calls Interested in organizing DjangoCon Europe 2016? | Weblog | Django Could you host DjangoCon Europe 2017? | Weblog | Django DjangoCon Europe 2019 - where will it be? | Weblog | Django Could you host DjangoCon Europe 2023? | Weblog | Django Last Chance for a DjangoCon Europe 2023 | Weblog | Django Want to host DjangoCon Europe 2024? | Weblog | Django DjangoCon Europe 2025 Call for Proposals | Weblog | Django Last call for DjangoCon Europe 2025 organizers | Weblog | Django Could you host DjangoCon Europe 2026? Call for organizers | Weblog | Django