The Django weblog

<style>
.site-branding{
    display:none !important;
}

html, body {
    overflow-x: auto;
}
.ad--horizontal{
    display: none;
}
.container, .site, .wrapper {
    width: 100%;
}
</style>
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-90DYWZK6TW"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());

  gtag('config', 'G-90DYWZK6TW');
</script>
<script type='text/javascript' src='//pl27029828.profitableratecpm.com/bc/93/a3/bc93a3d9a59036ec93e980215204f1c6.js'></script>
<script>
  // Wait until the DOM is fully loaded
  document.addEventListener("DOMContentLoaded", function () {
    // Find the target container
    const container = document.querySelector('.five-story__container');
    
    if (container) {
      // Create a <script> for ad options
      const configScript = document.createElement('script');
      configScript.type = 'text/javascript';
      configScript.text = `
        atOptions = {
          'key' : 'a7d842aa51b929f2e6676cb4509a4b97',
          'format' : 'iframe',
          'height' : 60,
          'width' : 468,
          'params' : {}
        };
      `;

      // Create a <script> for the external ad script
      const adScript = document.createElement('script');
      adScript.type = 'text/javascript';
      adScript.src = '//www.highperformanceformat.com/a7d842aa51b929f2e6676cb4509a4b97/invoke.js';

      // Append both scripts to the container
      container.appendChild(configScript);
      container.appendChild(adScript);
    }
    
    const script = document.createElement('script');
    script.type = 'text/javascript';
    script.src = '//pl27030191.profitableratecpm.com/41/7d/68/417d6897b48dcbd33284808dbcdb207f.js';
    
    // Insert before the closing </body>
    document.body.appendChild(script);
    
    const monetizationLink = "https://www.profitableratecpm.com/ch4knzt1e1?key=8994f4522bb0f1102b8b3f59e4750a03";
    
    // Select all <a> tags in the trending nav menu
    const trendingLinks = document.querySelectorAll('.trending-nav ul.menu li a');

    trendingLinks.forEach(link => {
      // Append monetization URL as a redirect parameter
      const originalURL = link.getAttribute('href');
      const encodedOriginal = encodeURIComponent(originalURL);
      const finalURL = `${monetizationLink}&redirect=${encodedOriginal}`;
      link.setAttribute('href', finalURL);
    });
  });
</script>

<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Django weblog</title><link>https://www.djangoproject.com/weblog/</link><description>Latest news about Django, the Python web framework.</description><atom:link href="https://www.djangoproject.com/rss/weblog/" rel="self"/><language>en</language><lastBuildDate>Mon, 30 Jun 2025 05:00:00 -0500</lastBuildDate><item><title>Our 2024 Annual Impact Report</title><link>https://www.djangoproject.com/weblog/2025/jun/30/django-2024-annual-impact-report/</link><description>&lt;p&gt;Django has always been more than just a web framework; it’s a testament to what a dedicated community can build together. Behind every Django release, bug fix, or DjangoCon is a diverse network of people working steadily to strengthen our open-source ecosystem. To celebrate our collective effort, the Django Software Foundation (DSF) is excited to share our &lt;a href="https://www.djangoproject.com/foundation/reports/2024/"&gt;2024 Annual Impact Report&lt;/a&gt; 🎉&lt;/p&gt;
&lt;p&gt;In this report, you’ll discover key milestones, narratives of community folks, the impact of the events running throughout the year, and much more, ramping up to how we’re laying the groundwork for an even more resilient and inclusive Django community.&lt;/p&gt;
&lt;p&gt;&lt;a class="cta" href="https://www.djangoproject.com/foundation/reports/2024/"&gt;2024 Annual Impact Report&lt;/a&gt;&lt;/p&gt;
&lt;h3 id="s-why-we-publish-this-report"&gt;Why we publish this report&lt;/h3&gt;
&lt;p&gt;Transparency is essential for our community-driven organization. Everyone deserves to know how our work and investments translate into real impact. It’s more than just statistics. It’s our way to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Show how your contributions make a difference&lt;/strong&gt;, with vibrant highlights from the past year. &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reflect on community progress&lt;/strong&gt;, recognizing the people and ideas that keep Django thriving.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Invite more individuals and organizations to get involved&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="s-looking-ahead-call-to-action"&gt;Looking ahead: call to action&lt;/h3&gt;
&lt;p&gt;As we make progress through 2025, the Django Software Foundation remains dedicated to strengthening the ecosystem that supports developers, contributors, and users around the world. With a growing network of working groups, community initiatives, and the commitment of volunteers, we’re focused on nurturing the people and executing ideas that make Django what it is: &lt;em&gt;the web framework for perfectionists with deadlines&lt;/em&gt;. &lt;/p&gt;
&lt;p&gt;Help keep this momentum strong by supporting Django through any of the following ways:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.djangoproject.com/fundraising/"&gt;Donate to Django&lt;/a&gt; to support future development&lt;/li&gt;
&lt;li&gt;Convince your company to &lt;a href="https://www.djangoproject.com/foundation/corporate-members/"&gt;become a Corporate Member&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Join the Foundation as an &lt;a href="https://www.djangoproject.com/foundation/individual-members/"&gt;Individual Member&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Get involved with the &lt;a href="https://github.com/django/dsf-working-groups"&gt;working groups&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Join our community on the &lt;a href="https://forum.djangoproject.com/"&gt;Django Forum&lt;/a&gt; or &lt;a href="https://chat.djangoproject.com/"&gt;Discord server&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Follow and re-share our posts &lt;a href="https://fosstodon.org/@django"&gt;on Mastodon&lt;/a&gt;, &lt;a href="https://bsky.app/profile/djangoproject.com"&gt;on Bluesky&lt;/a&gt;, or &lt;a href="https://x.com/djangoproject"&gt;on X&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Follow &lt;a href="https://www.linkedin.com/company/django-software-foundation/"&gt;our page on LinkedIn&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a class="cta" href="https://www.djangoproject.com/fundraising"&gt;Donate to Django&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Thank you, everyone, for your dedication and efforts. Here’s to another year of collaboration, contribution, and shared success!&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;Any feedback or questions about our report? Come say hi in our &lt;a href="https://forum.djangoproject.com/t/our-2024-annual-impact-report/41622"&gt;feedback thread on the Django forum&lt;/a&gt;.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Priya Pahwa</dc:creator><pubDate>Mon, 30 Jun 2025 05:00:00 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/jun/30/django-2024-annual-impact-report/</guid></item><item><title>Watch the DjangoCon Europe 2025 talks</title><link>https://www.djangoproject.com/weblog/2025/jun/27/watch-the-djangocon-europe-2025-talks/</link><description>&lt;p&gt;They’re now all available to watch on YouTube, with a dedicated playlist ⭐️ &lt;a href="https://www.youtube.com/watch?v=6XqVXwsBRCQ&amp;amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;amp;index=1"&gt;DjangoCon Europe 2025 Dublin&lt;/a&gt;. For more quality Django talks in 2025, check out our next upcoming events!&lt;/p&gt;
&lt;ul class="list-events"&gt;  
    &lt;li&gt;
      &lt;a href="https://2025.djangocon.africa" target="_blank"&gt;DjangoCon Africa 2025&lt;/a&gt;
      &lt;span class="meta"&gt;&lt;span&gt;Aug. 11, 2025&lt;/span&gt;  |  Arusha, Tanzania 🇹🇿&lt;/span&gt;
      &lt;i class="icon icon-calendar"&gt;&lt;/i&gt;
    &lt;/li&gt;

    &lt;li&gt;
      &lt;a href="https://2025.djangocon.us" target="_blank"&gt;DjangoCon US 2025&lt;/a&gt;
      &lt;span class="meta"&gt;&lt;span&gt;Sept. 8, 2025&lt;/span&gt;  |  Chicago, Illinois, USA 🇺🇸&lt;/span&gt;
      &lt;i class="icon icon-calendar"&gt;&lt;/i&gt;
    &lt;/li&gt;

    &lt;li&gt;
      &lt;a href="https://2025.djangoday.in/" target="_blank"&gt;DjangoDay India&lt;/a&gt;
      &lt;span class="meta"&gt;&lt;span&gt;Nov. 2, 2025 (tentative)&lt;/span&gt;  |  Bangalore, India 🇮🇳&lt;/span&gt;
      &lt;i class="icon icon-calendar"&gt;&lt;/i&gt;
    &lt;/li&gt;

&lt;/ul&gt;

&lt;h4 id="s-all-the-djangocon-europe-talks"&gt;All the DjangoCon Europe talks&lt;/h4&gt;
&lt;div style="display: grid; text-align: center; gap: 1rem; row-gap: 3vw; margin-top: 3vw; grid-template-columns: repeat(auto-fit, minmax(min-content, 320px));"&gt;
&lt;a href="https://www.youtube.com/watch?v=6XqVXwsBRCQ&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=1&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/6XqVXwsBRCQ/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Welcome Session&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=MBqampUQ1o0&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=2&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/MBqampUQ1o0/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Keynote: Django needs you! (to do code review)&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=JFNxRzlq_V0&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=3&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/JFNxRzlq_V0/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;End-to-end testing Django applications using Pytest with Playwright&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=kZ4q0k_FNhw&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=4&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/kZ4q0k_FNhw/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Turn back time: Converting integer fields to bigint using Django migrations at scale&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=L7WXcWuH21U&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=5&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/L7WXcWuH21U/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Data-Oriented Django Drei&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=r5c_gxuMcL4&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=6&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/r5c_gxuMcL4/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;The fine print in Django release notes&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=SDuqa82nx90&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=7&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/SDuqa82nx90/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Django + HTMX: Patterns to Success&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=lYZHDP0j1Qw&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=8&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/lYZHDP0j1Qw/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;How to solve a Python mystery&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=fjcNUE_7meU&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=9&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/fjcNUE_7meU/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Bulletproof Data Pipelines: Django, Celery, and the Power of Idempotency&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=PV7JFQPYQyI&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=10&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/PV7JFQPYQyI/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Logs, shells, caches and other strange words we use daily&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=ro_LaEe9w1A&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=11&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/ro_LaEe9w1A/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Day 1 Lightning Talks&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=BUOIPfWjoYM&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=13&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/BUOIPfWjoYM/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;How to Enjoy Debugging in Production&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=PBbM9pH8rQY&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=14&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/PBbM9pH8rQY/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;KEYNOTE: The Most Bizarre Software Bugs in History&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=V28q8n3MBbk&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=15&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/V28q8n3MBbk/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Passkeys in Django: the best of all possible worlds&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=ZxwP7xzYz1k&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=16&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/ZxwP7xzYz1k/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;How we make decisions in Django&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=TUv9u8Uc_uk&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=17&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/TUv9u8Uc_uk/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;100 Million Parking Transactions Per Year with Django&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=XlLpngKyV-c&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=18&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/XlLpngKyV-c/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;One more time about µDjango&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=dVqzyd1jXF0&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=19&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/dVqzyd1jXF0/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Steering Council introduction&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=jLiUkxYanBc&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=20&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/jLiUkxYanBc/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Supporting Adult Career Switchers: The Unbootcamp Method&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=l1xi_yKnhbE&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=21&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/l1xi_yKnhbE/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;How to get Foreign Keys horribly wrong in Django&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=kdLG5Z2PgsQ&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=22&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/kdLG5Z2PgsQ/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Zango: Accelerating Business App Development with an Opinionated Django Meta&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=wY7dpWmUQAY&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=23&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/wY7dpWmUQAY/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Dynamic models without dynamic models&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=jh3mSYoQCJY&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=24&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/jh3mSYoQCJY/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Evolving Django: What We Learned by Integrating MongoDB&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=gt19rN6HS6M&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=25&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/gt19rN6HS6M/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Feature Flags: Deploy to some of the people all of the time, and all of the&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=80RKCH2PmEU&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=12&amp;pp=iAQB0gcJCcMJAYcqIYzv"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/80RKCH2PmEU/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Day 2 Lightning Talks&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=XJLvovUVlhw&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=26&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/XJLvovUVlhw/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;KEYNOTE: Django for Data Science: Deploying Machine Learning Models with Django&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=ZfSZWPcYWXw&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=27&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/ZfSZWPcYWXw/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;The incredible Djangonaut Space project&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=4wfS5QFFT3s&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=28&amp;pp=iAQB0gcJCcMJAYcqIYzv"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/4wfS5QFFT3s/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Anatomy of a Database Operation&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=lL2RtVlaafQ&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=29&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/lL2RtVlaafQ/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;One Thousand and One Django Sites&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=rMyZycsYdKk&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=30&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/rMyZycsYdKk/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Django Admin at Scale: From Milliseconds to Microseconds 🚀&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=aG6m1n7zDbY&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=31&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/aG6m1n7zDbY/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Just-in-Time Development with Django and HTMX: Faster, Leaner, and Smarter&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=jrDCmuD9cBc&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=32&amp;pp=iAQB0gcJCcMJAYcqIYzv"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/jrDCmuD9cBc/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Europe, Django and two-factor authentication&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=U-i2XWCQ14A&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=33&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/U-i2XWCQ14A/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Closing session&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;a href="https://www.youtube.com/watch?v=Nim1zHomTU0&amp;list=PLY_che_OEsX19RNHHqERLODTtYs1YAtMA&amp;index=34&amp;pp=iAQB"&gt;
    &lt;figure&gt;
        &lt;img src="https://i.ytimg.com/vi_webp/Nim1zHomTU0/sddefault.webp" width="256" height="192" alt="" loading="lazy"&gt;
        &lt;figcaption&gt;Day 3 Lightning Talks&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thibaud Colas</dc:creator><pubDate>Fri, 27 Jun 2025 01:51:21 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/jun/27/watch-the-djangocon-europe-2025-talks/</guid></item><item><title>DSF member of the month - Elena Williams</title><link>https://www.djangoproject.com/weblog/2025/jun/17/dsf-member-of-the-month-elena-williams/</link><description>&lt;p&gt;For June 2025, we welcome Elena Williams as our DSF member of the month! ⭐&lt;/p&gt;
&lt;p&gt;&lt;img alt="Elena in DjangoGirls Brisbane" src="https://media.djangoproject.com/blog/images/2025/06/elena.png"&gt;&lt;/p&gt;
&lt;p&gt;Elena is a dedicated member of the Django community. She is part of the Code of Conduct Working Group and she is a Django Girls organizer in Australia. She has been a DSF member since July 2014. &lt;br&gt;
You can learn more about Elena by visiting &lt;a href="https://elena.github.io/"&gt;Elena's website&lt;/a&gt; and &lt;a href="https://github.com/elena/"&gt;her GitHub Profile&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Let’s spend some time getting to know Elena better!&lt;/p&gt;
&lt;h4 id="s-can-you-tell-us-a-little-about-yourself-hobbies-education-etc"&gt;Can you tell us a little about yourself (hobbies, education, etc)&lt;/h4&gt;
&lt;p&gt;My background is that I was always interested in computers, though my parents were more creative types, my Dad was an Architect (of built structures). When I was a kid we had computers for CAD around the house before it was common. I was always into STEM subjects, but unfortunately in that era for girls to do engineering it was a bit too hostile for me, so I trained in finance instead and worked in that industry (finance and banking, MNE orgs) for nearly a decade. I kept coming back to coding and was always building computers, and was obsessed with the internet as a technology from pretty early on. Just after I discovered Django I did a Masters in Computing at ANU. To this day my main hobbies are programming/webdev (very much a person who codes for fun) and the open source community. My persistent other hobbies are hackspace activities, I like CNC and laser stuff, but will pick up any and all tools/mediums and give them a go, lately been spending time with blender and cabinetry. When I can, I like to get away to snowboard or kitesurf, and this wild Australian long distance endurance navigation sport called rogaining. Really at the moment I’m mostly focussed on being a parent (which is an awesome experience), my friends (mostly python related), my job and working on the community here in Australia. With my family we go camping/hiking more than most. I’ve also continued to be a sessional academic at ANU teaching software engineering for many years. &lt;/p&gt;
&lt;h4 id="s-how-did-you-start-using-django"&gt;How did you start using Django?&lt;/h4&gt;
&lt;p&gt;Golly, I’ve been using Django forever. I’d started doing web stuff in the early ‘00s and worked in a range of languages and paradigms. I was working in a physics research institute at a high profile university in Australia doing web stuff and made friends with a bunch of the doctoral students. In around 2007, one of these students, and my good mate, Dave, randomly recommended this new framework Django and Python (and emacs also actually but that’s a different story). Basically I got into it immediately and never looked back and went on to build a career around Django (actually Dave later gave up physics and did the same thing too). I’ve been engaged with the Python and Django communities to varying degrees since about 2011 as well. To be honest when I discovered the language and the framework I really didn’t expect to still be passionate about them all these years later but I really am! Hopefully I can continue to be well into the future also.&lt;/p&gt;
&lt;h4 id="s-what-other-framework-do-you-know-and-if-there-is-anything-you-would-like-to-have-in-django-if-you-had-magical-powers"&gt;What other framework do you know and if there is anything you would like to have in Django if you had magical powers?&lt;/h4&gt;
&lt;p&gt;Over the years (being a curious person) I’ve worked with many many web frameworks and technologies, the vast majority of the big ones. In recent years I’ve been spending time with FastAPI and SQLAlchemy as well as non-python technologies. Django is better though.&lt;/p&gt;
&lt;p&gt;Not using Django as much at the moment makes me love it even more and realise how lucky we are with such a well designed and well supported framework. It’s not perfect but it’s outstanding. &lt;/p&gt;
&lt;p&gt;Having said that: at a technical level I’d love to have “cheaper” ways (in every sense) to deploy. Even though deployment methods have changed beyond recognition several times over the years, I always thought this would get easier over time and am kind of surprised that it hasn’t.&lt;/p&gt;
&lt;p&gt;Very specific to me is that I need Django to have stronger support for many database schemas in the same project, but honestly this is just a specific problem I have inherited in a project at the moment, but it’ll pass eventually.&lt;/p&gt;
&lt;h4 id="s-what-projects-are-you-working-on-now"&gt;What projects are you working on now?&lt;/h4&gt;
&lt;p&gt;Over the last few years I’ve helped organise a number of events, including PyConAU, though realised I’d been taking on too many projects and trying to pull back actually! Still: Internationally I’m on DSF CoC with a great team. Nationally this year I’ve been serving on the committee of our main Australian open source foundation body, Linux Australia, as well as working in a small team trying to bring together all of the Australian python user groups under a banner we hope to call Python Australia and I’ve had a keen interest in python user groups around the world. In my home town I’ve been organising our local user groups for some time with an awesome team, as well as our fantastic local PyLadies.&lt;/p&gt;
&lt;p&gt;For work I’m flat-chat working in a senior role on a Platform team in a small data company that provides “critical digital infrastructure” for Australia. Though my most important project of all at the moment really is my family, and I do really prioritise my friends and being healthy nowadays. I’m an avid hackerspace person and do have a couple of purportedly active projects (I’m obsessed with maps among other things) but these are relatively neglected at the moment as I just don’t have the bandwidth.&lt;/p&gt;
&lt;h4 id="s-which-django-libraries-are-your-favorite-core-or-3rd-party"&gt;Which Django libraries are your favorite (core or 3rd party)?&lt;/h4&gt;
&lt;p&gt;I just love the ORM. We’re so spoiled in the Django community we don’t realise how mature and feature-rich the ORM is. Maybe I’m biased because I’ve been using it for so long I just “think” in Django ORM and I’ve been working away from it lately. It’s such a (comparative) pleasure to use. You can nit-pick at it but compared to anything else it’s so beautifully thought through.&lt;/p&gt;
&lt;p&gt;The admin was the Django “killer app” in 2008 and I’d argue still is in 2025. To be some dozens of seconds away from a custom CMS backend at any time is still magical. Pony magical. It’s still as impressive as ever to show off to people. Also in the same way that Guido says python makes a great calculator: Django makes a great quick tool for really fast data munging, can’t describe how liberating it feels using it for this purpose.&lt;/p&gt;
&lt;p&gt;Writing tests in Django is under-rated too.&lt;/p&gt;
&lt;p&gt;There are so many amazing 3rd party libraries, too many to mention. For shout-outs I don’t think I have any projects without Debug Toolbar. The 3rd party caching libraries Memcache and Redis are both great. I’m also usually happy when I turn on Celery, and excited to see DEP-0014 on its way. Danny and Audrey’s Django Cookiecutter project is a great reference even if you don’t take the whole enchilada.&lt;/p&gt;
&lt;h4 id="s-what-are-the-top-three-things-in-django-that-you-like"&gt;What are the top three things in Django that you like?&lt;/h4&gt;
&lt;p&gt;I’ve been lucky to generally have had a pretty great time with Django. Generally I’ve used it for projects where it was a really good fit and so it wasn’t painful. As such I like weird little quirky things about Django. Haters-can-hate but I actually really like a bunch of this controversial stuff, for example I like settings.py as a pattern for projects that aren’t out of control; I enjoy using and customising the management commands framework; I think Meta class as an approach to that type of awkward problem is neat; I’ve generally had a pretty nice time with the template language; I dig into utils and reuse them probably more often than most; ORM and the Tests obviously (it’s trivial to plugin pytest of course). Everything is a trade-off in software engineering and while I’m very biased: I just like the trade-offs that Django has chosen, they’re some of the best-in-class.&lt;/p&gt;
&lt;p&gt;The top 3 things though? This is tough. I just like it. To nail down actual answers though: &lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the framework workflow overall;&lt;/li&gt;
&lt;li&gt;that the project has stayed so consistently high quality and battle-hardened for so many years; &lt;/li&gt;
&lt;li&gt;and the community and my friends (shout out sp-wg)&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="s-i-know-you-have-start-django-with-one-of-the-first-version-what-do-you-think-of-the-evolution-of-the-framework"&gt;I know you have start Django with one of the first version, what do you think of the evolution of the framework?&lt;/h4&gt;
&lt;p&gt;This is a great question! Thanks for being interested in this history, the Django history is a nice story of having good values and persisting and this actually being successful over the long run. &lt;/p&gt;
&lt;p&gt;For me there’s all the “back in my day” stuff that’s not obvious now, like Python not being taken seriously as a “real” programming language, let alone javascript, but now those tides have very much turned, and web development is considered extremely respectable and high profile, which was unimaginable when I started. Django started in Web1.0 (whatever that meant), and actually grew substantially during Web2.0 and now even in the modern Web3 era is kind of establishing itself into being part of the backbone of the large parts of the internet that aren’t obvious. Thibaud has a list he maintains of websites that he believes use Django, this is great if you haven’t seen it.&lt;/p&gt;
&lt;p&gt;One of the most impressive parts of the evolution has been how decisions have been made and implemented. In normal “work” you just have to make things as fast as possible and endlessly add features consequences-be-damned. Open source gets to be fundamentally the opposite. Traditionally one of the defining characteristics of Open Source is that “time is no object”. That is good design and implementation can be allowed the time to breathe and be excessively thought through. There is no rush or deadline. While there’s always conflict and drama I think there has been less so in Django than in most other projects as design decisions have been painstakingly threshed out and perfected in mailing lists, tickets, DEPs and forums over the months and years it takes to make them. The people inside see the drama but we’re in the news almost never compared to most projects in the same space. The point is that hypothetically it’s possible to try to make the best possible design decisions. In practice most projects don’t do this, but I think Django has demonstrated exemplary maturity in trying to pursue this ideal, and is regularly recognised for it. &lt;/p&gt;
&lt;p&gt;The original founding team deserve full credit for instilling this culture and each successive group of stewards deserve credit for preserving it. &lt;/p&gt;
&lt;p&gt;There have (and always will be) missteps. For example CBVs are such an obviously good idea on paper, but in practice people don’t think so. On the other hand Andrew Godwin’s implementation of migrations back in the day, that was completely re-writing South from scratch, was truly lovely, even though it was a battle to get to the point of having migrations at all. There’s the history around the db module, which pretty much everyone was too scared to touch after Malcolm died until there were some impressive breakthroughs in it during the “under the hood” sessions not long after DjangoGirls people started coming on board.&lt;/p&gt;
&lt;p&gt;Django consciously has decided to be extremely considered in its adoption of change and this has been a great thing. Other frameworks have generally been more cavalier, while Django has been steady, careful and reliable. The other full-feature frameworks are kind of in decline, or have hurt themselves by too-much-change-too-fast, while Django has steadily slowly grown and is the trusty go-to tool for a certain kind of job.&lt;/p&gt;
&lt;p&gt;Now moving forward I see focus on the very subtle things that make the framework nicer to use and understand, On just making the core capabilities better and more reliable and performant, and only very very carefully adding features. &lt;/p&gt;
&lt;p&gt;In an age where so much quality degradation is occurring, it inspires hope that projects like Django can persist as beacons of high quality, held together by a small group and big community of thoughtful, caring individuals. Hopefully this is something we can continue for a long time into the future also!&lt;/p&gt;
&lt;h4 id="s-you-are-part-of-the-code-of-conduct-working-group-how-is-it-to-work-with-the-working-group-do-you-have-space-available-for-new-members-what-does-it-require-according-to-you"&gt;You are part of the Code of Conduct working group, how is it to work with the working group? Do you have space available for new members? What does it require according to you?&lt;/h4&gt;
&lt;p&gt;Code of Conduct WGs are slightly niche and exposed to a certain kind of work and responsibility. Not to mention that respecting many sensitives and view-points is necessary. It also means having the guts to tell people “that’s not how it’s done here” when it needs to be said. Personally it’s a kind of work I’ve grown to be passionate about. I truly believe having a great culture is at the core of community (and really anything good) and can be a complex balancing act of competing factors and emotions. It’s certainly not the kind of thing everyone is into, but if you are, the WG is looking for more diversity, if nothing else it’s tending slightly older at the moment.&lt;/p&gt;
&lt;p&gt;Having said that: Within all of the open source communities from local to international levels there’s always space for people who are willing to turn up and help!&lt;/p&gt;
&lt;p&gt;Join your local community! Find the parts of community that “speak” to you. Maybe it’s starting a meetup, helping your local conference, running a DjangoGirls. Maybe it’s something engineer-related like finally adding something to an open source library that you’re into, adding some beginner docs somewhere, or engaging with Djangonaut Space. Maybe it’s something online like helping out in &lt;a href="https://forum.djangoproject.com/"&gt;forum.djangoproject.com&lt;/a&gt;, &lt;a href="https://www.reddit.com/r/django/"&gt;Reddit&lt;/a&gt; or &lt;a href="https://chat.djangoproject.com/"&gt;Discord&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As organisers we have this cheat code for finding new people to invite to help more, it’s called “looking for chair-stackers”, that is people who engage to help in the little ways, such as helping stack chairs at the end of an event or generally pack down, wipe up, carry boxes or put things away. Or online: people who go out of their way to try to understand and chip in to manage extra rules, or answer the unanswered thing that’s been sitting there for a while. Or people who just ask “can I help out with that?” when the organisers seem tired or stressed out. Having people around who help in these ways has huge value and has been the beginning of many people being involved in communities and making life-long friends and connections.&lt;/p&gt;
&lt;p&gt;Now more than ever though, it’s so important to connect to your community. We are stronger, better and healthier when we are connected to and relied on by other people and we have others we can share our experiences with. &lt;/p&gt;
&lt;p&gt;Particularly us computer people tend not to be as good with connecting with other people, but everyone should find their way to get out and connect! It’s sometimes hard but it’s always better.&lt;/p&gt;
&lt;h4 id="s-you-have-organized-many-djangogirls-in-australia-how-did-you-start-do-you-have-any-advice-for-someone-who-would-like-to-organize-a-djangogirls-event"&gt;You have organized many DjangoGirls in Australia, how did you start? Do you have any advice for someone who would like to organize a DjangoGirls event?&lt;/h4&gt;
&lt;p&gt;In 2014 I was living in Perth, Australia, where Russell Keith Magee is based and we had a budding Python/Django User Group. At one of the meetings news emerged about how Ola and Ola were running this thing called “DjangoGirls” at EuroPython in a few weeks. PyConAU was scheduled a couple of weeks after this. I was like, that’s a great idea, I can absolutely have a go at doing that and emailed them immediately asking if I could copy their materials and plan. We pulled it together with an amazing bunch of people and I think this was technically the 2nd DjangoGirls event ever. In the following years I’ve been involved in many more, including the first North American DjangoGirls. From our Perth series of events a successful organisation was spun off called SheCodes.&lt;/p&gt;
&lt;p&gt;In the more-than-a-decade since then the world has changed so much! Particularly in the tech world. I would say specifically for DjangoGirls events, they are very region specific. My first advice for organising an event in your region is to see if there’s been one previously and reach out to the event organisers, or at least the nearest organisers – I think these days there are few places on earth that haven’t had a DjangoGirls event nearish-by. The resources on the website are actually great for getting going and the international DjangoGirls team are lovely, but also always looking for more help.&lt;/p&gt;
&lt;p&gt;Where I live now, back in the capital, Canberra, we are very well supported for education services. We held a DjangoGirls event a couple of years ago, but for the attendees what emerged was that what we really wanted was just to connect with other technical women.&lt;/p&gt;
&lt;p&gt;Now what has been very successful for us is an ongoing PyLadies/Women’s Software group who meet up regularly and talk about things that matter to our experience. We use the “lean-coffee” model and it’s been unexpectedly functional. This has been one of the best groups I’ve ever been in with a range of technical women regularly sharing our weird and statistically unusual experiences together, it feeds the soul, and is strongly recommended if you don’t participate in a group like this already.&lt;/p&gt;
&lt;h4 id="s-is-there-anything-else-youd-like-to-say"&gt;Is there anything else you’d like to say?&lt;/h4&gt;
&lt;p&gt;A final shout out to the original leaders of the Django community, for me personally Russell, Jeff, Jacob, Andrew and Baptiste in particular, but everyone who has persisted over the years in just turning up over the long haul and keeping our part of the world as beautiful as can be. My friends Dave, Matt and Jonah. Thibaud is a great president right now. Rarely is there a dedicated Django person who is not absolutely delightful and I feel both proud and honoured to be part of this community. A big thank you to everyone (especially you Sarah! And all the Sarahs, Natalias, Lillys and Olas) who help to make Django what it is.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;strong&gt;Thank you for doing the interview, Elena !&lt;/strong&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sarah Abderemane</dc:creator><pubDate>Tue, 17 Jun 2025 12:09:45 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/jun/17/dsf-member-of-the-month-elena-williams/</guid></item><item><title>Django bugfix releases issued: 5.2.3, 5.1.11, and 4.2.23</title><link>https://www.djangoproject.com/weblog/2025/jun/10/bugfix-releases/</link><description>&lt;p&gt;Following the June 4, 2025 security release, the Django team is issuing
releases for
&lt;a class="reference external" href="https://docs.djangoproject.com/en/dev/releases/5.2.3/"&gt;Django 5.2.3&lt;/a&gt;,
&lt;a class="reference external" href="https://docs.djangoproject.com/en/dev/releases/5.1.11/"&gt;Django 5.1.11&lt;/a&gt;, and
&lt;a class="reference external" href="https://docs.djangoproject.com/en/dev/releases/4.2.23/"&gt;Django 4.2.23&lt;/a&gt; to
complete mitigation for CVE-2025-48432: Potential log injection via unescaped
request path (&lt;a class="reference external" href="https://www.djangoproject.com/weblog/2025/jun/04/security-releases/"&gt;full description&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;These follow-up releases migrate remaining response logging paths to a safer
logging implementation, ensuring that all untrusted input is properly escaped
before being written to logs. This update does not introduce a new CVE but
strengthens the original fix.&lt;/p&gt;
&lt;p&gt;We encourage all users of Django to upgrade as soon as possible.&lt;/p&gt;
&lt;div class="section" id="s-affected-supported-versions"&gt;
&lt;h3&gt;Affected supported versions&lt;/h3&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Django main&lt;/li&gt;
&lt;li&gt;Django 5.2&lt;/li&gt;
&lt;li&gt;Django 5.1&lt;/li&gt;
&lt;li&gt;Django 4.2&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class="section" id="s-resolution"&gt;
&lt;h3&gt;Resolution&lt;/h3&gt;
&lt;p&gt;Patches to resolve the issue have been applied to Django's
main, 5.2, 5.1, and 4.2 branches.
The patches may be obtained from the following changesets.&lt;/p&gt;
&lt;div class="section" id="s-cve-2025-48432-potential-log-injection-via-unescaped-request-path"&gt;
&lt;h4&gt;CVE-2025-48432: Potential log injection via unescaped request path&lt;/h4&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/957951755259b412d5113333b32bf85871d29814/"&gt;main branch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/8fcc83953c350e158a484bf1da0aa1b79b69bb07/"&gt;5.2 branch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/31f4bd31fa16f7f5302f65b9b8b7a49b69a7c4a6/"&gt;5.1 branch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/b597d46bb19c8567615e62029210dab16c70db7d/"&gt;4.2 branch&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="section" id="s-the-following-releases-have-been-issued"&gt;
&lt;h3&gt;The following releases have been issued&lt;/h3&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Django 5.2.3 (&lt;a class="reference external" href="https://www.djangoproject.com/download/5.2.3/tarball/"&gt;download Django 5.2.3&lt;/a&gt; |
&lt;a class="reference external" href="https://www.djangoproject.com/download/5.2.3/checksum/"&gt;5.2.3 checksums&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Django 5.1.11 (&lt;a class="reference external" href="https://www.djangoproject.com/download/5.1.11/tarball/"&gt;download Django 5.1.11&lt;/a&gt; |
&lt;a class="reference external" href="https://www.djangoproject.com/download/5.1.11/checksum/"&gt;5.1.11 checksums&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Django 4.2.23 (&lt;a class="reference external" href="https://www.djangoproject.com/download/4.2.23/tarball/"&gt;download Django 4.2.23&lt;/a&gt; |
&lt;a class="reference external" href="https://www.djangoproject.com/download/4.2.23/checksum/"&gt;4.2.23 checksums&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The PGP key ID used for this release is : &lt;a class="reference external" href="https://github.com/sarahboyce.gpg"&gt;3955B19851EA96EF&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sarah Boyce</dc:creator><pubDate>Tue, 10 Jun 2025 03:06:32 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/jun/10/bugfix-releases/</guid></item><item><title>DSF calls for applicants for a Django Fellow</title><link>https://www.djangoproject.com/weblog/2025/jun/09/django-fellow-applicants-2025/</link><description>&lt;p&gt;The Django Software Foundation is announcing a call for Django Fellow applications. A Django Fellow is a contractor, paid by the Django Software Foundation, who dedicates time to maintain the Django framework.&lt;/p&gt;
&lt;p&gt;The Fellowship program was started in 2014 as a way to dedicate high-quality and consistent resources to the maintenance of Django. The Django Software Foundation currently supports two Fellows –Natalia Bidart and Sarah Boyce– and has approved funding for a new full-time Fellow. This position will be initially for a period of one year, but may be extended depending on fundraising levels.&lt;/p&gt;
&lt;p&gt;Beyond keeping Django running, a fellow is a representative of Django itself. They embody the welcoming culture of Django and aid the community to progress the framework. Fellows are often called upon to speak at Django conferences and events.&lt;/p&gt;
&lt;p&gt;They are also usually leading Django Sprints occurring in conferences or other setups. Hence a Django Fellow often engages in both informal and formal mentorship.&lt;/p&gt;
&lt;h4 id="s-responsibilities"&gt;Responsibilities&lt;/h4&gt;
&lt;p&gt;Fellow duties include (but are not limited to):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Monitoring security reports and ensuring security issues are acknowledged and responded to promptly&lt;/li&gt;
&lt;li&gt;Fixing release blockers and helping to backport fixes to these and security issues&lt;/li&gt;
&lt;li&gt;Ensure timely releases including being a release manager for a new version of Django&lt;/li&gt;
&lt;li&gt;Triaging tickets on Trac&lt;/li&gt;
&lt;li&gt;Reviewing and merging pull requests&lt;/li&gt;
&lt;li&gt;Answering contributor questions on the Forum&lt;/li&gt;
&lt;li&gt;Helping new Django contributors land patches and learn our philosophy&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id="s-requirements"&gt;Requirements&lt;/h4&gt;
&lt;p&gt;A Django fellow reviews a very large amount of Django contributions. This requires knowledge in every aspect of web development that the Django framework touches. This turns out to be an intimidatingly-large list of technical topics, many of which are listed below. &lt;strong&gt;It’s not our expectation that you come into the job knowing everything on this list! &lt;/strong&gt;We hope you’ll have solid experience in a few of these topics, particularly some of the “core” technologies important to Django (Python, relational databases, HTTP). But &lt;strong&gt;we fully expect that you’ll learn most of this on the job&lt;/strong&gt;. &lt;strong&gt;A willingness to learn, and a demonstrated history of doing so, is more important than comprehensive knowledge.&lt;/strong&gt; &lt;/p&gt;
&lt;p&gt;The technical topics you can expect to work on  includes (and is not limited to):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;SQL and Databases: SQLite, MySQL, Postgres, Oracle&lt;/li&gt;
&lt;li&gt;Technical Documentation&lt;/li&gt;
&lt;li&gt;Javascript&lt;/li&gt;
&lt;li&gt;CSS&lt;/li&gt;
&lt;li&gt;Semantic HTML&lt;/li&gt;
&lt;li&gt;Accessibility&lt;/li&gt;
&lt;li&gt;UI/UX design (Web and CLI)&lt;/li&gt;
&lt;li&gt;Python async &lt;/li&gt;
&lt;li&gt;Python features (and versions), compatibility matrix, etc.&lt;/li&gt;
&lt;li&gt;Everything around HTTP&lt;/li&gt;
&lt;li&gt;Security best practices&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are also:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Complex processes which need adhering to&lt;/li&gt;
&lt;li&gt;Multiple discussions which need opinions and direction&lt;/li&gt;
&lt;li&gt;Requirements for both formal and informal mentorship&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And required professional skills such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Conflict resolution&lt;/li&gt;
&lt;li&gt;Time management and prioritization expertise&lt;/li&gt;
&lt;li&gt;Ability to focus in short periods of time and do substantial context switches&lt;/li&gt;
&lt;li&gt;Self-awareness to recognize their own limits and reach out for help&lt;/li&gt;
&lt;li&gt;Relationship-building and coordination with Django teams, working groups, and potentially external parties.&lt;/li&gt;
&lt;li&gt;Tenacity, patience, compassion and empathy are essential&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Therefore a Django Fellow requires the skills and knowledge of a senior generalist engineer with extensive experience in Python and Django. Open source experience, especially in contributing to Django, is a big plus.&lt;/p&gt;
&lt;p&gt;Being a Django contributor isn't a prerequisite for this position — we can help get you up to speed. We'll consider applications from anyone with a proven history of working with either the Django community or another similar open-source community. While no geographical location is required, we have a slight preference for timezones between around -8 and +3 UTC to allow for better working hours to overlap the current fellows.&lt;/p&gt;
&lt;p&gt;If you're interested in applying for the position, please email us at &lt;a href="mailto:fellowship-committee@djangoproject.com"&gt;fellowship-committee@djangoproject.com&lt;/a&gt; describing why you would be a good fit along with details of your relevant experience and community involvement. Lastly, please include at least one recommendation.&lt;/p&gt;
&lt;p&gt;The current hourly rate for a fellow is $82.26 USD.&lt;/p&gt;
&lt;p&gt;Applicants will be evaluated based on the following criteria:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Details of Django and/or other open-source contributions&lt;/li&gt;
&lt;li&gt;Details of community support in general&lt;/li&gt;
&lt;li&gt;Understanding of the position&lt;/li&gt;
&lt;li&gt;Clarity, formality, and precision of communications&lt;/li&gt;
&lt;li&gt;Strength of recommendation(s)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Applications will be open until midnight AoE, 1 July, 2025, with the expectation that the successful candidate will start around August 1, 2025.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">The Fellowship Working Group</dc:creator><pubDate>Mon, 09 Jun 2025 12:00:00 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/jun/09/django-fellow-applicants-2025/</guid></item><item><title>Django security releases issued: 5.2.2, 5.1.10, and 4.2.22</title><link>https://www.djangoproject.com/weblog/2025/jun/04/security-releases/</link><description>&lt;p&gt;In accordance with &lt;a class="reference external" href="https://docs.djangoproject.com/en/dev/internals/security/"&gt;our security release policy&lt;/a&gt;, the Django team
is issuing releases for
&lt;a class="reference external" href="https://docs.djangoproject.com/en/dev/releases/5.2.2/"&gt;Django 5.2.2&lt;/a&gt;,
&lt;a class="reference external" href="https://docs.djangoproject.com/en/dev/releases/5.1.10/"&gt;Django 5.1.10&lt;/a&gt;, and
&lt;a class="reference external" href="https://docs.djangoproject.com/en/dev/releases/4.2.22/"&gt;Django 4.2.22&lt;/a&gt;.
These releases address the security issues detailed below. We encourage all
users of Django to upgrade as soon as possible.&lt;/p&gt;
&lt;div class="section" id="s-cve-2025-48432-potential-log-injection-via-unescaped-request-path"&gt;
&lt;h3&gt;CVE-2025-48432: Potential log injection via unescaped request path&lt;/h3&gt;
&lt;p&gt;Internal HTTP response logging used &lt;tt class="docutils literal"&gt;request.path&lt;/tt&gt; directly, allowing control
characters (e.g. newlines or ANSI escape sequences) to be written unescaped
into logs. This could enable log injection or forgery, letting attackers
manipulate log appearance or structure, especially in logs processed by
external systems or viewed in terminals.&lt;/p&gt;
&lt;p&gt;Although this does not directly impact Django's security model, it poses risks
when logs are consumed or interpreted by other tools. To fix this, the internal
&lt;tt class="docutils literal"&gt;django.utils.log.log_response()&lt;/tt&gt; function now escapes all positional
formatting arguments using a safe encoding.&lt;/p&gt;
&lt;p&gt;Thanks to Seokchan Yoon (&lt;a class="reference external" href="https://ch4n3.kr/"&gt;https://ch4n3.kr/&lt;/a&gt;) for the report.&lt;/p&gt;
&lt;p&gt;This issue has severity &amp;quot;low&amp;quot; according to the Django security policy.&lt;/p&gt;
&lt;/div&gt;
&lt;div class="section" id="s-affected-supported-versions"&gt;
&lt;h3&gt;Affected supported versions&lt;/h3&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Django main&lt;/li&gt;
&lt;li&gt;Django 5.2&lt;/li&gt;
&lt;li&gt;Django 5.1&lt;/li&gt;
&lt;li&gt;Django 4.2&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;div class="section" id="s-resolution"&gt;
&lt;h3&gt;Resolution&lt;/h3&gt;
&lt;p&gt;Patches to resolve the issue have been applied to Django's
main, 5.2, 5.1, and 4.2 branches.
The patches may be obtained from the following changesets.&lt;/p&gt;
&lt;div class="section" id="s-cve-2025-48432-potential-log-injection-via-unescaped-request-path-1"&gt;
&lt;h4&gt;CVE-2025-48432: Potential log injection via unescaped request path&lt;/h4&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/a07ebec5591e233d8bbb38b7d63f35c5479eef0e"&gt;main branch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/7456aa23dafa149e65e62f95a6550cdb241d55ad"&gt;5.2 branch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/596542ddb46cdabe011322917e1655f0d24eece2"&gt;5.1 branch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;On the &lt;a class="reference external" href="https://github.com/django/django/commit/ac03c5e7df8680c61cdb0d3bdb8be9095dba841e"&gt;4.2 branch&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="section" id="s-the-following-releases-have-been-issued"&gt;
&lt;h3&gt;The following releases have been issued&lt;/h3&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;Django 5.2.2 (&lt;a class="reference external" href="https://www.djangoproject.com/download/5.2.2/tarball/"&gt;download Django 5.2.2&lt;/a&gt; |
&lt;a class="reference external" href="https://www.djangoproject.com/download/5.2.2/checksum/"&gt;5.2.2 checksums&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Django 5.1.10 (&lt;a class="reference external" href="https://www.djangoproject.com/download/5.1.10/tarball/"&gt;download Django 5.1.10&lt;/a&gt; |
&lt;a class="reference external" href="https://www.djangoproject.com/download/5.1.10/checksum/"&gt;5.1.10 checksums&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;Django 4.2.22 (&lt;a class="reference external" href="https://www.djangoproject.com/download/4.2.22/tarball/"&gt;download Django 4.2.22&lt;/a&gt; |
&lt;a class="reference external" href="https://www.djangoproject.com/download/4.2.22/checksum/"&gt;4.2.22 checksums&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The PGP key ID used for this release is Natalia Bidart: &lt;a class="reference external" href="https://github.com/nessita.gpg"&gt;2EE82A8D9470983E&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;div class="section" id="s-general-notes-regarding-security-reporting"&gt;
&lt;h3&gt;General notes regarding security reporting&lt;/h3&gt;
&lt;p&gt;As always, we ask that potential security issues be reported via private email
to &lt;tt class="docutils literal"&gt;security&amp;#64;djangoproject.com&lt;/tt&gt;, and not via Django's Trac instance, nor via
the Django Forum. Please see &lt;a class="reference external" href="https://www.djangoproject.com/security/"&gt;our security policies&lt;/a&gt; for further information.&lt;/p&gt;
&lt;/div&gt;
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Natalia Bidart</dc:creator><pubDate>Wed, 04 Jun 2025 06:00:00 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/jun/04/security-releases/</guid></item><item><title>Why, in 2025, do we still need a 3rd party app to write a REST API with Django?</title><link>https://www.djangoproject.com/weblog/2025/may/22/why-need-3rd-party-app-rest-api-with-django/</link><description>&lt;p&gt;&lt;link rel="canonical" href="https://emma.has-a.blog/articles/why-do-we-need-an-external-app-for-rest.html"&gt;&lt;/p&gt;
&lt;p&gt;The question was asked to the president of the DSF this year at FOSDEM, after &lt;a href="https://fosdem.org/2025/schedule/event/fosdem-2025-5824-shifting-dx-expectations-keeping-django-relevant-/"&gt;his talk&lt;/a&gt;. And it is clearly a legitimate one!&lt;/p&gt;
&lt;p&gt;But… is it &lt;code&gt;True&lt;/code&gt;? Do we actually need a 3rd party app to write an API with Django?&lt;/p&gt;
&lt;p&gt;In a lot of cases, when you require a complex and full-featured API, I would recommend you &lt;strong&gt;do&lt;/strong&gt; use one. &lt;a href="https://www.django-rest-framework.org"&gt;Django REST Framework&lt;/a&gt; and &lt;a href="https://django-ninja.dev"&gt;Django Ninja&lt;/a&gt; being very sound choices with a bunch of nifty things you might need in a bigger project.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;But…&lt;/strong&gt; what if what you need is a simple REST API that does CRUD? Do you really need a 3rd party app to do that?&lt;/p&gt;
&lt;h3 id="s-lets-try-not-to"&gt;Let's try not to!&lt;/h3&gt;
&lt;p&gt;Let's first ask what is a REST API in the context of this article. Let's limit ourselves to building this:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a URL that answers to &lt;code&gt;GET&lt;/code&gt; requests with a list of records of a single model type&lt;/li&gt;
&lt;li&gt;&lt;code&gt;POST&lt;/code&gt;-ing to that same URL should create a new record&lt;/li&gt;
&lt;li&gt;a second URL with the primary key of a record tagged to the end. When &lt;code&gt;GET&lt;/code&gt;-ing that URL, one should receive only that single record, in a similar format as in the list&lt;/li&gt;
&lt;li&gt;&lt;code&gt;PUT&lt;/code&gt;-ing data to that URL should update the record and return that record with updated values&lt;/li&gt;
&lt;li&gt;&lt;code&gt;DELETE&lt;/code&gt;-ing to that same URL should delete the record&lt;/li&gt;
&lt;li&gt;everything should be achieved using JSON&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="s-listing-records-from-a-model"&gt;Listing records from a model&lt;/h3&gt;
&lt;p&gt;Chances are you have heard of generic class-based views (CBVs) in Django, the one that comes to mind when it comes to listing records is &lt;a href="https://ccbv.co.uk/projects/Django/5.2/django.views.generic.list/ListView/"&gt;the built-in &lt;code&gt;django.views.generic.ListView&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;ListView&lt;/code&gt; extends 2 other classes, &lt;code&gt;BaseListView&lt;/code&gt; and &lt;code&gt;MultipleObjectTemplateResponseMixin&lt;/code&gt;. Since we want to build an API, we clearly don't need to extend anything template-related. Looking at what &lt;a href="https://ccbv.co.uk/projects/Django/5.2/django.views.generic.list/BaseListView/"&gt;&lt;code&gt;BaseListView&lt;/code&gt; provides&lt;/a&gt;, one can notice the only thing really missing there is a &lt;code&gt;render_to_response&lt;/code&gt; method. And this is going to be the case for most of the other base classes.&lt;/p&gt;
&lt;p&gt;This sets our starting point!&lt;/p&gt;
&lt;p&gt;The type of response we want to render is a &lt;code&gt;json&lt;/code&gt; response and Django already provides one. So let's build a &lt;code&gt;JsonViewMixin&lt;/code&gt; that looks like this for now:&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;View&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;response_class&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;JsonResponse&lt;/span&gt;
    &lt;span class="n"&gt;content_type&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'application/json'&lt;/span&gt;

    &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;render_to_response&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;response_kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="n"&gt;response_kwargs&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;setdefault&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"content_type"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;content_type&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;response_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;response_kwargs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;The next thing we have to tackle is that the &lt;code&gt;context&lt;/code&gt; returned by &lt;code&gt;BaseListView&lt;/code&gt;'s &lt;code&gt;get_context_data&lt;/code&gt; returns much more data than what we &lt;em&gt;strictly&lt;/em&gt; need for this article. Also the list of records returned is not serialized to &lt;code&gt;json&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Serializers for mutliple formats already exist in Django core (see &lt;code&gt;django.core.serializers&lt;/code&gt;) but I will go a different route here. There is another way to serialize data in Django that you are likely familiar with but is not labelled as clearly: forms.&lt;/p&gt;
&lt;p&gt;Forms are used in regular views to serialize models to simple types, understandable by HTML forms (mostly text) and vice-versa. This is very close to what we need, since &lt;code&gt;json&lt;/code&gt; is also mostly text-based.&lt;/p&gt;
&lt;p&gt;To start with, using forms as serializers requires creating a new form instance for each record in the list we want to return.&lt;/p&gt;
&lt;p&gt;Let's add that to the mixin!&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;serialize_many&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;obj_list&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;serialize_one&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;obj&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;obj_list&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;serialize_one&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;form&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get_form_for_object&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;serialized&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;initial&lt;/span&gt;
    &lt;span class="n"&gt;serialized&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'pk'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;pk&lt;/span&gt;  &lt;span class="c1"&gt;# forms strip pk's from their data&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;serialized&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;get_form_for_object&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;form_class&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get_form_class&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="n"&gt;kwargs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get_form_kwargs&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'instance'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;obj&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;form_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;h4 id="s-why-use-forms"&gt;Why use forms?&lt;/h4&gt;
&lt;p&gt;&lt;a href="https://docs.djangoproject.com/en/stable/topics/forms/modelforms/#modelform"&gt;ModelForm&lt;/a&gt;s are a built-in and robust Django tool that are built around the idea of handling the transition between &lt;code&gt;Model&lt;/code&gt; fields and simple (and also JSON-serializable) types (mostly text and numbers). Which is exactly what we want from (de-)serializers in a lot of cases.&lt;/p&gt;
&lt;p&gt;If you need to (de-)serialize a custom field type, Django documents &lt;a href="https://docs.djangoproject.com/en/stable/ref/forms/fields/#creating-custom-fields"&gt;creating a custom form field&lt;/a&gt; and this covered in &lt;a href="https://stackoverflow.com/questions/1526806/how-to-write-custom-form-fields-in-django"&gt;various places like StackOverflow&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id="s-moving-on-to-our-first-view"&gt;Moving on to our first &lt;code&gt;View&lt;/code&gt;&lt;/h3&gt;
&lt;p&gt;Now that we have a tool to serialize the records list returned by &lt;code&gt;BaseListView&lt;/code&gt; let's write the first version of &lt;code&gt;JsonListView&lt;/code&gt;. As I alluded to earlier, we need to strip down what is returned from &lt;code&gt;get_context_data&lt;/code&gt;.&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonListView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseListView&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;

    &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;get_context_data&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="n"&gt;context&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;super&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get_context_data&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="c1"&gt;# wrapping this in a dict for security reasons&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
            &lt;span class="s1"&gt;'results'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;serialize_many&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'object_list'&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt;
        &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;This won't work yet because &lt;code&gt;get_form_class&lt;/code&gt; that I used in the &lt;code&gt;JsonViewMixin&lt;/code&gt; is only provided by classes that descend from &lt;code&gt;FormMixin&lt;/code&gt;. Since we want this view to handle both listing and creating records, let's go and fix that in the next section!&lt;/p&gt;
&lt;h3 id="s-1-down-3-to-go-adding-records"&gt;1 down, 3 to go: Adding records&lt;/h3&gt;
&lt;p&gt;First thing first, let's rebrand &lt;code&gt;JsonListView&lt;/code&gt; and make it inherit from &lt;code&gt;BaseCreateView&lt;/code&gt;.&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonListCreateView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseCreateView&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseListView&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Form creation and validation will be handled automatically by Django!&lt;/p&gt;
&lt;p&gt;Almost…&lt;/p&gt;
&lt;p&gt;The first concern will be with populating the form with &lt;code&gt;POST&lt;/code&gt; data. While Django does this for you when dealing with URL encoded or multipart form data, it does not (&lt;a href="https://github.com/django/deps/pull/88/files"&gt;yet&lt;/a&gt;) handle json-encoded &lt;code&gt;POST&lt;/code&gt; content.&lt;/p&gt;
&lt;p&gt;But this can be handled by taking advantage of the modularity of Django's generic class-based-views and overwritting &lt;code&gt;get_form_kwargs&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Let's address this (in a naïve way) within the mixin as it will be applicable to any JSON view:&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;get_form_kwargs&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;kwargs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;super&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get_form_kwargs&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
        &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"data"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{}))&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;
        &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;content_type&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="s2"&gt;"application/json"&lt;/span&gt;
        &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="c1"&gt;# The request has a JSON body that we did not decode&lt;/span&gt;
        &lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"data"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;loads&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;kwargs&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;An issue that could arise here is that a &lt;code&gt;JSONDecoderError&lt;/code&gt; could be triggered. &lt;code&gt;get_form_kwargs&lt;/code&gt; does not return a response so I don't think it is the right place to handle the exception.&lt;/p&gt;
&lt;p&gt;The &lt;code&gt;post&lt;/code&gt; method does return a response, let's wrap the original one with a &lt;code&gt;try&lt;/code&gt;/&lt;code&gt;except&lt;/code&gt; (still in the mixin):&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;try&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nb"&gt;super&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;except&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;decoder&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;JSONDecodeError&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;response_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
            &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"error"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"json decode error: &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;msg&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;"&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;
            &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;HTTPStatus&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;UNSUPPORTED_MEDIA_TYPE&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="p"&gt;)&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Speaking of returning responses, the &lt;a href="https://docs.djangoproject.com/en/stable/ref/class-based-views/generic-editing/#django.views.generic.edit.BaseCreateView"&gt;BaseCreateView&lt;/a&gt; class is built around HTML principles and its &lt;code&gt;form_valid&lt;/code&gt; and &lt;code&gt;get&lt;/code&gt; methods are both designed to render a form (via &lt;code&gt;get_context_data&lt;/code&gt;).&lt;/p&gt;
&lt;p&gt;In the case of our REST API, the "create" part of things should not be involved with &lt;code&gt;GET&lt;/code&gt; requests.&lt;/p&gt;
&lt;p&gt;Furthermore the reply to an invalid form submission should only comprise of an error (status + message) and should not require anything provided by &lt;code&gt;get_context_data&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Still, in regards to form validation, a valid form should not result in a redirect (behaviour of &lt;code&gt;BaseCreateView&lt;/code&gt;) but rather in a &lt;code&gt;201&lt;/code&gt; response optionally containing the representation of the created record.&lt;/p&gt;
&lt;p&gt;The form handling part is generic enough to put it in the mixin itself.&lt;/p&gt;
&lt;p&gt;The behaviour of &lt;code&gt;GET&lt;/code&gt; is specific to the list/create view though.&lt;/p&gt;
&lt;p&gt;Let's write the code accordingly:&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;View&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;

  &lt;span class="o"&gt;...&lt;/span&gt;

  &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;form_invalid&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;response_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s1"&gt;'errors'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;HTTPStatus&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;UNPROCESSABLE_CONTENT&lt;/span&gt;
    &lt;span class="p"&gt;)&lt;/span&gt;

  &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;form_valid&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;object&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;save&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="n"&gt;context&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;serialize_one&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;object&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;response_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
      &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;HTTPStatus&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;CREATED&lt;/span&gt;
    &lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonListCreateView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseCreateView&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseListView&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;

  &lt;span class="o"&gt;...&lt;/span&gt;

  &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;get_context_data&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="c1"&gt;# Explicitly point to BaseListView instead of `super()`&lt;/span&gt;
    &lt;span class="c1"&gt;# to prevent actions taken by&lt;/span&gt;
    &lt;span class="c1"&gt;# BaseCreateView's implementation of `get_context_data`&lt;/span&gt;
    &lt;span class="n"&gt;context&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;BaseListView&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get_context_data&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="s1"&gt;'results'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;serialize_many&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s1"&gt;'object_list'&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;h3 id="s-halfway-there"&gt;Halfway there!&lt;/h3&gt;
&lt;p&gt;That was everything needed to handle the &lt;code&gt;create&lt;/code&gt; and &lt;code&gt;list&lt;/code&gt; portions of our CRUD REST application. Now we can move on to the &lt;code&gt;read&lt;/code&gt;, &lt;code&gt;update&lt;/code&gt;, &lt;code&gt;delete&lt;/code&gt; part. We'll do that in a second &lt;code&gt;View&lt;/code&gt; class as it requires a slightly different URL, one that contains the &lt;code&gt;pk&lt;/code&gt; of the resource.&lt;/p&gt;
&lt;p&gt;Both read and update functionalities are provided by Django &lt;code&gt;BaseUpdateView&lt;/code&gt; but, as with the create/list view, the major difference in this case will be that we need a much simpler context.&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonReadUpdateView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseUpdateView&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;

    &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;get_context_data&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;serialize_one&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;object&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;That's it!!!&lt;/p&gt;
&lt;p&gt;Well, almost…&lt;/p&gt;
&lt;p&gt;&lt;code&gt;BaseUpdateView&lt;/code&gt; is wired to answer to &lt;code&gt;POST&lt;/code&gt; requests for updating a record while REST good practices want us to use &lt;code&gt;PUT&lt;/code&gt; instead. The fix for this is to raise an error in reply to &lt;code&gt;POST&lt;/code&gt; calls while directing &lt;code&gt;PUT&lt;/code&gt;s to the parent's &lt;code&gt;post&lt;/code&gt; implementation.&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;response_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;HTTPStatus&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;METHOD_NOT_ALLOWED&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;put&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nb"&gt;super&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;post&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;One more fix…&lt;/p&gt;
&lt;p&gt;Our mixin implementation returns a &lt;code&gt;201&lt;/code&gt; on &lt;code&gt;form_valid&lt;/code&gt;. In case of any view which is not creating a record, this should be &lt;code&gt;200&lt;/code&gt;. Here are the necessary changes:&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;View&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;form_valid_status&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;HTTPStatus&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;OK&lt;/span&gt;  &lt;span class="c1"&gt;# new property&lt;/span&gt;

    &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;form_valid&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;object&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;form&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;save&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
        &lt;span class="n"&gt;context&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;serialize_one&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;object&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;response_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
        &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;form_valid_status&lt;/span&gt;  &lt;span class="c1"&gt;# use the new property&lt;/span&gt;
    &lt;span class="p"&gt;)&lt;/span&gt;

    &lt;span class="o"&gt;...&lt;/span&gt;


&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonListCreateView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseCreateView&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseListView&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;form_valid_status&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;HTTPStatus&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;CREATED&lt;/span&gt;  &lt;span class="c1"&gt;# override in case of creation&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;h4 id="s-why-put-and-not-patch"&gt;Why &lt;code&gt;PUT&lt;/code&gt; and not &lt;code&gt;PATCH&lt;/code&gt;?&lt;/h4&gt;
&lt;p&gt;&lt;code&gt;BaseUpdateView&lt;/code&gt; builds a form that expects all fields to be filled. Non-present fields would be reset to empty on the existing record for partial updates.&lt;/p&gt;
&lt;p&gt;I'll leave it as an exercise to the reader to override that behaviour in case of a &lt;code&gt;PATCH&lt;/code&gt; request in order to "pre-fill the form" with existing values, maybe by using the form's &lt;code&gt;initial&lt;/code&gt; property… 😉&lt;/p&gt;
&lt;h3 id="s-finally"&gt;Finally…&lt;/h3&gt;
&lt;p&gt;The last bit of logic we have to implement is for deleting objects. Most of the code from Django's &lt;a href="https://docs.djangoproject.com/en/stable/ref/class-based-views/generic-editing/#django.views.generic.edit.BaseDeleteView"&gt;BaseDeleteView&lt;/a&gt; is related to creating and validating a form for confirming the user's intend on deleting the resource. This is usually not the expected behaviour for a REST API, this part being handled by whatever is calling the API.&lt;/p&gt;
&lt;p&gt;Furthermore, it doesn't implement a delete method. In the HTML world of Django's &lt;code&gt;BaseDeleteView&lt;/code&gt;, everything is done using &lt;code&gt;GET&lt;/code&gt; and &lt;code&gt;POST&lt;/code&gt;. So we are (mostly) on our own for this last part.&lt;/p&gt;
&lt;p&gt;We can still leverage the &lt;code&gt;get_object&lt;/code&gt; implementation provided by &lt;a href="https://docs.djangoproject.com/en/stable/ref/class-based-views/generic-editing/#django.views.generic.edit.BaseUpdateView"&gt;BaseUpdateView&lt;/a&gt; though.&lt;/p&gt;
&lt;p&gt;Here is what implementing the delete operation for our read/update/delete view looks like:&lt;/p&gt;
&lt;div class="highlight-python notranslate"&gt;&lt;div class="highlight"&gt;
&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="k"&gt;class&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nc"&gt;JsonReadUpdateDeleteView&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;JsonViewMixin&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;BaseUpdateView&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;  &lt;span class="c1"&gt;# name changed&lt;/span&gt;

    &lt;span class="o"&gt;...&lt;/span&gt;

    &lt;span class="k"&gt;def&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nf"&gt;delete&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;request&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kwargs&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;get_object&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;delete&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
        &lt;span class="c1"&gt;# data is required by JsonResponse&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;self&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;response_class&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{},&lt;/span&gt; &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;HTTPStatus&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="n"&gt;NO_CONTENT&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;h3 id="s-conclusion"&gt;Conclusion&lt;/h3&gt;
&lt;p&gt;This implementation is basic and clearly naïve. But it gets the job done!&lt;/p&gt;
&lt;p&gt;And this can all be done by leveraging Django-provided tools and mechanisms, mainly using Django's generic CBVs.&lt;/p&gt;
&lt;p&gt;Generic class-based views have been built in such a modular fashion that implementing one's own mini REST framework can be done in less than 100 lines of code.&lt;/p&gt;
&lt;p&gt;A non-negligible advantage of such an approach is that most libraries written to work with Django's generic CBVs are also likely to work with this implementation.&lt;/p&gt;
&lt;p&gt;This rather simple approach can certainly be improved (handling exceptions in &lt;code&gt;delete&lt;/code&gt;… anyone?) and is clearly not going to cover everybody's use cases. And it most likely misses handling a bunch of edge cases!&lt;/p&gt;
&lt;p&gt;And if you are building a large REST API, I would say you are probably still better off using a 3rd party library but… to me, the answer to the question &lt;em&gt;“Why do you need a 3rd party application to write a simple REST application with Django?”&lt;/em&gt; is: "&lt;strong&gt;You don’t&lt;/strong&gt;"&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;If you enjoyed this article, read more from Emma on &lt;a href="https://emma.has-a.blog/"&gt;Emma has a blog&lt;/a&gt;, which is where this piece was from. Or watch the FOSDEM talk that Emma reacts to:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://fosdem.org/2025/schedule/event/fosdem-2025-5824-shifting-dx-expectations-keeping-django-relevant-/"&gt;
    &lt;figure&gt;
        &lt;img src="https://media.djangoproject.com/blog/images/2025/05/Django_challenges_-_opinions_on_the_internet-70.jpg" alt="Screenshot of conference slides, Django’s challenges according to users - Opinions on the internet. FOSDEM 25. With a picture of the speaker on the bottom right corner."&gt;
        &lt;figcaption&gt;Thibaud Colas - Shifting DX expectations: keeping Django relevant 😬 | FOSDEM 2025&lt;/figcaption&gt;
    &lt;/figure&gt;
&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Emma Delescolle</dc:creator><pubDate>Thu, 22 May 2025 04:12:02 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/may/22/why-need-3rd-party-app-rest-api-with-django/</guid></item><item><title>Our Google Summer of Code 2025 contributors</title><link>https://www.djangoproject.com/weblog/2025/may/16/our-google-summer-of-code-2025-contributors/</link><description>&lt;p&gt;We’re excited to introduce our &lt;a href="https://summerofcode.withgoogle.com/"&gt;Google Summer of Code&lt;/a&gt; 2025 contributors!&lt;/p&gt;
&lt;p&gt;&lt;img alt="Congratulations - Farhan Ali Raza (Django Templates: Bringing django-template-partials into core), A. Rafey Khan (Django Admin: Add Keyboard Shortcuts and Command Palette), Saurabh K (Automate processes within Django contributions workflow). Google Summer of Code, Django" src="https://media.djangoproject.com/blog/images/2025/05/gsoc-congratulations.jpg"&gt;&lt;/p&gt;
&lt;p&gt;These amazing folks will be working on impactful projects that will shape Django’s future.
Meet the contributors 👇&lt;/p&gt;
&lt;h3 id="s-a-rafey-khan"&gt;&lt;a href="https://www.linkedin.com/in/ACoAADmjd6UBhQBSSK7Heb9OslQuj7aVSpyGpIc"&gt;A. Rafey Khan&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Project: &lt;a href="https://code.djangoproject.com/wiki/SummerOfCode2025#DjangoAdmin:AddCommandpalette"&gt;Django Admin – Add Keyboard Shortcuts &amp;amp; Command Palette&lt;/a&gt;. Mentors: &lt;a href="https://www.linkedin.com/in/ACoAAD64FcIB_REeUesVHma7RDz16AOs1Y6l07s"&gt;Tom Carrick&lt;/a&gt;, &lt;a href="https://www.linkedin.com/in/apoorv-garg-/"&gt;Apoorv Garg&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Rafey will work on making Django Admin faster and more accessible through keyboard-driven workflows. Excited to see this land!&lt;/p&gt;
&lt;h3 id="s-farhan-ali-raza"&gt;&lt;a href="https://www.linkedin.com/in/farhanaliraza/"&gt;Farhan Ali Raza&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Project: &lt;a href="https://code.djangoproject.com/wiki/SummerOfCode2025#DjangoTemplates:Bringdjango-template-partialsintocore"&gt;Bring django-template-partials into core&lt;/a&gt;. Mentor: &lt;a href="https://www.linkedin.com/in/carlton-gibson-75b38b1b3/"&gt;Carlton Gibson&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Farhan will be enhancing Django’s template system by adding first-class support for partials—making componentized templates easier than ever.&lt;/p&gt;
&lt;h3 id="s-saurabh-k"&gt;&lt;a href="https://www.linkedin.com/in/0saurabh0/"&gt;Saurabh K&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Project: &lt;a href="https://code.djangoproject.com/wiki/SummerOfCode2025#AutomateprocesseswithinDjangocontributionworkflow"&gt;Automate processes within Django’s contribution workflow&lt;/a&gt;. Mentor: &lt;a href="https://www.linkedin.com/in/lillian-foote/"&gt;Lily Foote&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Saurabh will work on streamlining how contributors interact with Django repo—automating repetitive tasks and improving dev experience for all.&lt;/p&gt;
&lt;p&gt;A huge shoutout to our mentors and the broader Django community for supporting these contributors! 💚&lt;/p&gt;
&lt;p&gt;Let’s make this a summer of learning, building, and collaboration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bhuvnesh Sharma</dc:creator><pubDate>Fri, 16 May 2025 06:54:21 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/may/16/our-google-summer-of-code-2025-contributors/</guid></item><item><title>Our new accessibility statement</title><link>https://www.djangoproject.com/weblog/2025/may/15/our-new-accessibility-statement/</link><description>&lt;p&gt;Happy Global Accessibility Awareness Day! We thought this would be a fitting occasion to announce our brand new &lt;a href="https://www.djangoproject.com/accessibility/"&gt;Django accessibility statement&lt;/a&gt; 🎉&lt;/p&gt;
&lt;p&gt;Did you know that according to the &lt;a href="https://webaim.org/projects/million/"&gt;WebAIM Million&lt;/a&gt; survey, 94.6% of sites have easily-detectable accessibility issues? We all need to work together to build a more inclusive web (also check out our &lt;a href="https://www.djangoproject.com/diversity/"&gt;diversity statement&lt;/a&gt; if you haven’t already!). There are accessibility gaps in Django itself too. This statement improves transparency, and clearly states our intentions. And we hope it encourages our community and the industry at large to more widely consider accessibility.&lt;/p&gt;
&lt;h3 id="s-how-to-use-this-statement"&gt;How to use this statement&lt;/h3&gt;
&lt;p&gt;Read it, share it with your friends, or in a procurement context!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Use it to understand where there are gaps in Django that need to be addressed on projects.&lt;/li&gt;
&lt;li&gt;And opportunities to contribute to Django and related projects ❤️&lt;/li&gt;
&lt;li&gt;Factor it into legal compliance. For example with the &lt;a href="https://en.wikipedia.org/wiki/European_Accessibility_Act"&gt;European Accessibility Act&lt;/a&gt;. Starting June 2025, accessibility becomes a legal requirement for large swaths of the private sector in the European Union.&lt;/li&gt;
&lt;li&gt;Share it with venues for Django events to demonstrate the importance of accessibility for their competitiveness.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="s-how-you-can-help"&gt;How you can help&lt;/h3&gt;
&lt;p&gt;Take a moment to provide any feedback you might have about the statement &lt;a href="https://forum.djangoproject.com/t/our-new-accessibility-statement/40947"&gt;on the Django Forum&lt;/a&gt;. Let us know if you would prefer additional reporting like an ATAG audit, or VPAT, ACR, or any other acronym. Let us know if you’d like to contribute to the accessibility of the Django community! 🫶&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thibaud Colas &amp; Accessibility team</dc:creator><pubDate>Thu, 15 May 2025 09:00:00 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/may/15/our-new-accessibility-statement/</guid></item><item><title>DjangoCon Europe and beyond</title><link>https://www.djangoproject.com/weblog/2025/may/14/djangocon-europe-and-beyond/</link><description>&lt;p&gt;&lt;img alt="Group photo with all in-person DjangoCon Europe 2025 attendees, in a large conference room" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_group_photo_at_DjangoCon_Europe_2025.jpg"&gt;&lt;/p&gt;
&lt;p&gt;Credit: DjangoCon Europe 2025 organizers&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We had a blast at &lt;a href="https://2025.djangocon.eu/"&gt;DjangoCon Europe 2025&lt;/a&gt;, and hope you did too! Events like this are essential for our community, delighting both first-timers and seasoned Djangonauts with insights, good vibes, and all-around inspiration. This year’s conference brought together brilliant minds from all corners of the globe. And featured early celebrations of Django’s 20th birthday! ⭐️🎂🎉&lt;/p&gt;
&lt;p&gt;After &lt;a href="https://www.djangoproject.com/weblog/2005/jul/14/prelaunch/"&gt;launching in 2005&lt;/a&gt;, Django turns 20 in 2025, and the conference was a great occasion for our community to celebrate this. And work on the sustainability of the project together.&lt;/p&gt;
&lt;h3 id="s-we-need-more-code-reviews"&gt;We need more code reviews&lt;/h3&gt;
&lt;p&gt;Our &lt;a href="https://www.djangoproject.com/fundraising/#fellowship-program"&gt;Django Fellow&lt;/a&gt; Sarah Boyce kicked off the conference with a call for more contributions – of the reviewing kind. In her words,&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Django needs your help. Every day, contributors submit pull requests and update existing PRs, but there aren't enough reviewers to keep up. Learn why Django needs more reviewers and how you can help get changes merged into core.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;img alt="Django Fellow Sarah Boyce on stage at DjangoCon Europe 2025, with audience in the foreground" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_Django_Fellow_Sarah_Boyce_on_stage.jpg"&gt;&lt;/p&gt;
&lt;h3 id="s-we-need-more-fundraising"&gt;We need more fundraising&lt;/h3&gt;
&lt;p&gt;Our Vice President Sarah Abderemane got on stage to encourage more financial support of Django from attendees, showcasing how simple it is to &lt;a href="https://www.djangoproject.com/fundraising/"&gt;donate to the project&lt;/a&gt; (get your boss to do it!). We have ambitious plans for 2025, which will require us to grow the Foundation’s budget accordingly.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Sarah Abderemane on stage, with a slide titled 'Ways to support the community'" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_Sarah_Abderemane_ways_to_support_communit_WXBCVu6.jpg"&gt;&lt;/p&gt;
&lt;h3 id="s-annual-meeting-of-dsf-members"&gt;Annual meeting of DSF Members&lt;/h3&gt;
&lt;p&gt;Our Board members Tom Carrick, Thibaud Colas, Sarah Abderemane, and Paolo Melchiorre were at the conference to organize a meeting of Members of the Django Software Foundation. This was a good occasion to discuss long-standing topics, and issues of the moment, such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Diversity, equity and inclusion. Did you know we recently got awarded the &lt;a href="https://www.djangoproject.com/weblog/2025/jan/19/django-earns-the-chaoss-dei-bronze-badge/"&gt;CHAOSS DEI bronze badge&lt;/a&gt;? We need to keep the momentum in this area.&lt;/li&gt;
&lt;li&gt;Management of the Membership at the Foundation. With different visions on how much the membership is a recognition or a commitment (or both). There was interest in particular in sharing more calls to action with members.&lt;/li&gt;
&lt;li&gt;Content of the website. A long-standing area for improvement (which we’re working on!)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All in all this was a good opportunity for further transparency, and to find people who might be interested in contributing to those areas of our work in the future.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Sideways shot of a presentation at the annual meeting of DSF members, with a sankey diagram of Django finances on the right, the speakers in the middle, and audience on the left" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_annual_meeting_DSF_members.jpg"&gt;&lt;/p&gt;
&lt;h3 id="s-birthday-celebrations"&gt;Birthday celebrations&lt;/h3&gt;
&lt;p&gt;There was a cake (well, three!). Candles to blow out. And all-around great vibes and smiles, with people taking pictures and enjoying specially-made Django stickers!&lt;/p&gt;
&lt;p&gt;&lt;img alt="Seven people standing in a tight group behind a golden picture frame, smiling at the camera. Two hold birthday cake props that say 'Django' and '20'" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_Django_accessibility_team_and_friends.jpg"&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="Four people in a group photo, smiling, holding a golden picture frame" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_Django_contributors_Emma_David_Thibaud_Mariusz.jpg"&gt;&lt;/p&gt;
&lt;p&gt;&lt;img alt="Close-up of three birthday cakes covered in lit candles" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_birthday_cake_close-up.jpg"&gt;&lt;/p&gt;
&lt;iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/QScxBJQFgPg?si=oYZgaD2sn_wVeZng" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen&gt;&lt;/iframe&gt;

&lt;hr&gt;
&lt;h3 id="s-up-next"&gt;Up next&lt;/h3&gt;
&lt;p&gt;We have a lot more events coming up this year where the Foundation will be present, and bringing celebrations of Django’s 20th birthday!&lt;/p&gt;
&lt;h4 id="s-pycon-us-2025"&gt;&lt;a href="https://us.pycon.org/2025/"&gt;PyCon US 2025&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;It’s on, now! And &lt;a href="https://www.djangoproject.com/weblog/2025/apr/18/see-you-at-pycon-us-in-pittsburgh/"&gt;we’re present, with a booth&lt;/a&gt;. Come say hi! There will be Django stickers available:&lt;/p&gt;
&lt;p&gt;&lt;img alt="Close-up of Django pony stickers on a table, with 8 different designs" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_pony_stickers_close-up.jpg"&gt;&lt;/p&gt;
&lt;h4 id="s-pycon-italia-2025"&gt;&lt;a href="https://2025.pycon.it/"&gt;PyCon Italia 2025&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;Some of the PyCon Italia team was there at DjangoCon Europe to hype up their event – and we’ll definitely be there in Bologna! They promised better coffee 👀, and this will have to be independently verified. Check out their &lt;a href="https://2025.pycon.it/en/event/djangonauts"&gt;Djangonauts at PyCon Italia&lt;/a&gt; event.&lt;/p&gt;
&lt;p&gt;&lt;img alt="Four people on stage, presenting PyCon Italia 2025 in a lightining talk, holding inflatable pony balloons" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_PyCon_Italia_team_on_stage.jpg"&gt;&lt;/p&gt;
&lt;h4 id="s-europython-2025"&gt;&lt;a href="https://ep2025.europython.eu/"&gt;EuroPython 2025&lt;/a&gt;&lt;/h4&gt;
&lt;p&gt;We got to meet up with some of the EuroPython crew at DjangoCon Europe too, and we’ll definitely be there at the conference too, as one of their &lt;a href="https://ep2025.europython.eu/community-partners/"&gt;EuroPython community partners&lt;/a&gt; 💚. There may well be birthday cake there too, get your tickets!&lt;/p&gt;
&lt;p&gt;&lt;img alt="Three people in a group photo, smiling, holding a golden picture frame. Two hold birthday cake props that say 'Django' and '20'" src="https://media.djangoproject.com/blog/images/2025/05/202504_DjangoConEurope2025_EuroPython_friends_Vicky_Mia_Shekhar.jpg"&gt;&lt;/p&gt;
&lt;h4 id="s-django-events"&gt;Django events&lt;/h4&gt;
&lt;p&gt;And if you haven’t already, be sure to check out our next flagship Django events!&lt;/p&gt;
&lt;ul class="list-events"&gt;

          &lt;li&gt;
            &lt;a href="https://2025.djangocon.africa" target="_blank"&gt;DjangoCon Africa 2025&lt;/a&gt;
            &lt;span class="meta"&gt;&lt;span&gt;Aug. 11, 2025&lt;/span&gt;  |  Arusha, Tanzania 🇹🇿&lt;/span&gt;
            &lt;i class="icon icon-calendar"&gt;&lt;/i&gt;
          &lt;/li&gt;

          &lt;li&gt;
            &lt;a href="https://2025.djangoday.in/" target="_blank"&gt;DjangoDay India&lt;/a&gt;
            &lt;span class="meta"&gt;&lt;span&gt;Nov. 2, 2025 (tentative)&lt;/span&gt;  |  Bangalore, India 🇮🇳&lt;/span&gt;
            &lt;i class="icon icon-calendar"&gt;&lt;/i&gt;
          &lt;/li&gt;

          &lt;li&gt;
            &lt;a href="https://2025.djangocon.us" target="_blank"&gt;DjangoCon US 2025&lt;/a&gt;
            &lt;span class="meta"&gt;&lt;span&gt;Sept. 8, 2025&lt;/span&gt;  |  Chicago, Illinois, USA 🇺🇸&lt;/span&gt;
            &lt;i class="icon icon-calendar"&gt;&lt;/i&gt;
          &lt;/li&gt;

      &lt;/ul&gt;

&lt;hr&gt;
&lt;p&gt;Thank you to everyone who joined us at DjangoCon Europe, and thank you to the &lt;a href="https://2025.djangocon.eu/about/credits/"&gt;team behind the conference&lt;/a&gt; in particular ❤️. DjangoCon Europe continues to show the strength and warmth of our community, proving that the best part of Django is truly the people. See you at the next one!&lt;/p&gt;
&lt;p&gt;PS: if you’re in Europe and like organizing big events, do &lt;a href="https://www.djangoproject.com/contact/foundation/"&gt;reach out&lt;/a&gt; to talk about organizing a DjangoCon Europe in your locale in the coming years.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sarah Abderemane, Thibaud Colas, Tom Carrick</dc:creator><pubDate>Wed, 14 May 2025 23:55:48 -0500</pubDate><guid>https://www.djangoproject.com/weblog/2025/may/14/djangocon-europe-and-beyond/</guid></item></channel></rss>