# Django Django is a high-level Python web framework for building web applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Executive Director Search Extended to September 22 DevFeed: [Executive Director Search Extended to September 22]() Original publisher: [Read original article]() Author: Jeff Triplett and the DSF Board Published: 2026-09-16T12:50:40Z Content type: news Language: en Sources: [The Django weblog]() Topics: [Django](), [Open Source](), [Job]() Tags: [2026](), [communication](), [community](), [django](), [framework](), [fundraising](), [job](), [leadership](), [open-source](), [organizational](), [python](), [relationships]() ### AI overview The Django Software Foundation has extended applications for its first Executive Director through September 22, 2026, anywhere on Earth. The role focuses on fundraising, partnerships, operations, and supporting the Django community. ### Source excerpt We are extending the search for the Django Software Foundation's first Executive Director. Applications now close at the end of Tuesday, September 22, 2026, anywhere on Earth (AoE). As long as it is still September 22 somewhere, your application counts. We are happy with the applications we received. We also knew several people had applications in progress, and it took a while for word about the role to reach everyone it should have. Giving people a little more time felt like the fairest option. If you were most of the way there, you have until Tuesday. If you have already applied, this does not slow anything down for you. We are reviewing applications as they come in, and we will reach out to candidates and schedule interviews on the same timeline we planned. The Executive Director will play a central role in helping the DSF grow its capacity and build a sustainable future for the Django project and its community. That includes leading fundraising and partnerships, supporting the Foundation's operations and programs, and working closely with the board, staff, volunteers, and the wider Django community. We are looking for an experienced nonprofit leader who is comfortable taking on a broad role and building things as they go. Fundraising is central to this job. We need someone who is at ease sitting down with companies, making the case for Django, and connecting what the DSF does to what those organizations care about. Much of the Foundation's future depends on growing those relationships and turning them into steady support. You don't need to be a Django or Python expert, and you don't need prior involvement in the Django community. Experience with open source or other community-driven organizations is welcome, but we are primarily looking for someone with strong fundraising instincts, plus leadership, communication, relationship-building, and organizational skills. Could that person be you? If you have been waiting for the right opportunity to step forward, we enc ## DjangoCon Europe 2027 is heading to Innsbruck, Austria! 🏔⛷🚠🇦🇹 DevFeed: [DjangoCon Europe 2027 is heading to Innsbruck, Austria! 🏔⛷🚠🇦🇹]() Original publisher: [Read original article]() Author: DjangoCon Europe 2027 Organizing Team Published: 2026-09-15T13:20:26Z Content type: news Language: en Sources: [The Django weblog]() Topics: [Django](), [Python]() Tags: [announce](), [community](), [conference](), [django](), [framework](), [open-source](), [python]() ### AI overview DjangoCon Europe 2027 will take place in Innsbruck, Austria, from February 17-21, 2027. The community-run conference has opened its Call for Proposals and started ticket sales, with volunteer and sponsorship opportunities also available. ### Source excerpt We're delighted to announce that DjangoCon Europe 2027 will take place in Innsbruck, Austria, from February 17-21, 2027! Photo by Nicole Baster on Unsplash Each year, DjangoCon Europe brings together people from across the Django community to learn, share ideas, contribute, and spend time together. In 2027, that community will come together in Innsbruck for five days of Django, Python, and community. DjangoCon Europe is organized by community volunteers and has long been one of the highlights of the Django community calendar. Developers, contributors, newcomers, and long-time community members from around the world come together to exchange knowledge, make new connections, and help shape the future of Django. Save the dates 📅 February 17-21, 2027 📍 Innsbruck, Austria And there's even more good news: the Call for Proposals is open, and tickets are now on sale! Submit a proposal Have something you'd like to share with the Django community? The Call for Proposals is open. Whether you have a deep technical topic, a lesson you've learned from building with Django, an idea that could benefit the community, or something completely unexpected, we'd love to hear from you. Submit a proposal -> Get your ticket Ready to join us in Innsbruck? Tickets for DjangoCon Europe 2027 are now on sale. Come spend five days learning, sharing, meeting fellow Djangonauts, and enjoying everything the Django community has to offer. Get your ticket -> Volunteer at DjangoCon Europe DjangoCon Europe is a community-run conference, and volunteers play an important part in making it happen. If you'd like to help us make DjangoCon Europe 2027 a great experience for everyone, sign up to volunteer. Whether you're a long-time member of the community or attending your first DjangoCon, we'd love to have you involved. Sign up to volunteer -> Sponsor DjangoCon Europe Support the conference financially and gain visibility in the Django community. Learn more about sponsorship -> Download the sponsorship brochure ## The Real Python Podcast - Episode #311: Django Developers Survey Results & Reproducible Python Builds DevFeed: [The Real Python Podcast - Episode #311: Django Developers Survey Results & Reproducible Python Builds]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-11T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Django](), [Python](), [LLMs](), [releases]() Tags: [2026](), [developers](), [django](), [llms](), [news](), [podcast](), [python](), [reproducible-builds](), [survey]() ### AI overview Episode 311 discusses findings from the 2026 Django Developers Survey, including how Django users are adopting LLMs in their development workflows. It also covers reproducible Python builds, recent Python and Django ecosystem releases, community news, and projects such as matchify and pydantic-pint. ### Source excerpt What are the latest trends uncovered in the 2026 Django Developers Survey? How are Django users employing LLMs in their development process? Christopher Trudeau is back on the show this week with another batch of PyCoder's Weekly articles and projects. ## Call for volunteers: Fundraising Working Group DevFeed: [Call for volunteers: Fundraising Working Group]() Original publisher: [Read original article]() Author: Priya Pahwa Published: 2026-09-08T19:27:14Z Content type: article Language: en Sources: [The Django weblog]() Topics: [Django]() Tags: [building](), [business](), [community](), [development](), [django](), [ecosystem](), [events](), [executive](), [framework](), [infrastructure](), [leadership](), [open-source](), [partnerships](), [python](), [sales](), [support]() ### AI overview The Django Software Foundation is recruiting volunteers for a Fundraising Working Group as it pursues a 2026 fundraising goal of $500,000 and prepares to hire its first Executive Director. The group will help develop sponsorships, partnerships, donor relationships, and new fundraising initiatives for the Django project. ### Source excerpt The Django Software Foundation is looking for people to join the Fundraising Working Group. This is a particularly interesting time to get involved. The DSF has raised its 2026 fundraising goal to $500,000. That funding is what allows us to continue supporting the Django Fellows, Django Girls, community events, Djangonaut Space, infrastructure, and the many other things that keep the Django ecosystem going. It also gives the DSF the room to do something new: hire its first Executive Director. You can read more about the DSF's fundraising goals for 2026 in this post. Getting there will take more than asking people to donate. We need to think about how we build relationships with companies that depend on Django, how we make sponsorships meaningful, how we find new ways for organisations to support the project, and how we communicate the value of investing in Django. That is where the Fundraising Working Group comes in. The DSF is hiring an Executive Director who will bring dedicated, day-to-day leadership to the Foundation, including sponsorship development and partner relationships. The Fundraising Working Group will have an opportunity to work closely with the person in this role as we build out our fundraising efforts. Who are we looking for? We'd love to have people who have done this before. If you have experience with fundraising, sponsorships, partnerships, business development, sales, donor relationships, or building relationships with companies, there is plenty of scope to put that experience to work. We need people who can help identify opportunities, open doors, develop ideas, and turn them into actual fundraising initiatives. But you don't need to be a fundraising expert to join. Maybe you've never worked on fundraising before, but you know how companies make decisions about supporting open source. Maybe you have ideas for how Django could engage organisations that rely on it. Maybe you are good at building relationships, telling a compelling story, organi ## Django bugfix release issued: 6.1.1 DevFeed: [Django bugfix release issued: 6.1.1]() Original publisher: [Read original article]() Author: Jacob Walls Published: 2026-09-02T17:30:00Z Content type: release Language: en Sources: [The Django weblog]() Topics: [Django]() Tags: [django](), [framework](), [open-source](), [python](), [release]() ### AI overview Django 6.1.1 has been issued as a bugfix release, with the release package and checksums available for download. ### Source excerpt Today we've issued the 6.1.1 bugfix release. The release package and checksums are available from our downloads page, as well as from the Python Package Index. The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7 ## DSF member of the month - Benjamin Balder Bach DevFeed: [DSF member of the month - Benjamin Balder Bach]() Original publisher: [Read original article]() Author: Sarah Abderemane Published: 2026-08-31T05:00:00Z Content type: article Language: en Sources: [The Django weblog]() Topics: [Django](), [PHP](), [Computer science](), [HTML](), [SQL]() Tags: [community](), [developers](), [development](), [django](), [framework](), [open-source](), [php](), [python](), [sql](), [support]() ### AI overview An August 2026 Django community profile introduces Benjamin Balder Bach, highlighting his work with Django Day Copenhagen and the Social Media Working Group. He discusses his path from self-taught web designer to computer science and digital design studies, along with his experience using HTML, SQL, ASP classic, PHP, and Django. The interview connects Django's emphasis on rapid development with the importance of understanding users through developer involvement in frontline support. ### Source excerpt For August 2026, we welcome Benjamin Balder Bach as our DSF member of the month! ⭐ Benjamin has long been part of the Django community, serving for years as an organizer of Django Day Copenhagen and as Chair of the Social Media Working Group. He is a DSF member since June 2020! You can learn more about Benjamin by visiting Benjamin's website and his GitHub Profile. Let's spend some time getting to know Benjamin better! Can you tell us a little about yourself? (hobbies, education, etc) Hello! I like DIY in general, so whether it's software, cooking, sewing, growing plants or building stuff with wood - I really like practical things with a finish in sight. I really don't mind when it's not a software project, though 😇 I'll try to nail what my education and work is about: I started as a self-taught programmer when I had a job at 15 (as a web designer). Before that, I had been delivering newspapers and cleaning toilets at my school, so it was a pretty big leap forward. I knew HTML but learned about SQL and ASP classic (not .net) because my employer back in 2000 let me learn while working. Fast-forward, I studied Computer Science from 2005 and took my masters degree in Digital Design and Communication - heavily inspired by years of PHP and Django experience, my thesis ended up being about "Risky and Rapid Design Spaces" (2013) - a concept/anecdote that I still stand by. It becomes relevant in the context of Django because the front-and-center message and goal of the framework is to "encourages rapid development". "Rapid" means that we iterate and deploy changes quickly (with lots of aspects of what that means). But I think we need to understand and frame the "risky" part, especially understanding that a GIANT risk-avertion factor is to have developers understand and share context with users, whether they are clients, customers or staff colleagues. For instance, while I was working at Read the Docs, we had developers rotating on frontline support, meaning that everyone in ## Django Developers Survey 2026 results DevFeed: [Django Developers Survey 2026 results]() Original publisher: [Read original article]() Author: Jeff Triplett Published: 2026-08-28T14:55:00Z Content type: news Language: en Sources: [The Django weblog]() Topics: [Django](), [PyCharm](), [htmx](), [Artificial Intelligence](), [Deployment](), [Tooling]() Tags: [ai](), [blog](), [deployment](), [django](), [framework](), [htmx](), [open-source](), [pycharm](), [python](), [testing](), [tooling]() ### AI overview The Django Developers Survey 2026 results are available. The report was conducted by the Django Software Foundation with JetBrains PyCharm, and related coverage discusses Django trends, Django 6.1, HTMX, async development, AI, deployment, testing, and Python tooling. ### Source excerpt The results from the 2026 Django Developers Survey are now available. This is the fifth annual report conducted from May to July 2026 by the Django Software Foundation in collaboration with JetBrains PyCharm. The full report includes infographics, quotes, and dedicated sections so you can easily navigate the results. There is also a The State of Django 2026: Boring is so back blog post highlighting key Django trends in 2026 and actionable ideas for your own Django development. The Django Chat podcast also covers the survey in a special summer episode, from Django 6.1 and HTMX to async, AI, deployment, testing, and Python tooling. ## Python projects now support routing rules DevFeed: [Python projects now support routing rules]() Original publisher: [Read original article]() Author: Ricardo Gonzalez Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Routing (disambiguation)](), [Python](), [FastAPI](), [Django](), [Flask](), [Command-line interface](), [SDKs](), [Deployment](), [CI/CD](), [REST API]() Tags: [api](), [automation](), [ci-cd](), [cli](), [deployment](), [python](), [rest-api](), [routing](), [sdk](), [vercel]() ### AI overview Vercel now supports routing rules for Python projects, allowing response headers and request rewrites to internal paths for FastAPI, Django, and Flask applications. Rules are evaluated by the Vercel CDN before requests reach the application and can take effect immediately without a new deployment. ### Source excerpt Python projects can now use routing rules to set response headers or rewrite requests to internal paths, including apps built with FastAPI, Django, and Flask. The Vercel CDN evaluates rules before requests reach your application, so changes apply without a new deployment. For example, this FastAPI app serves a /new route: To send requests for /old to that route, create a rewrite from the CDN tab in your project dashboard or with the Vercel CLI: Published rules take effect immediately across all regions, and you can roll back to a previous version from the History tab. You can also manage rules from Python with the vercel SDK, which wraps the Vercel REST API. add_route stages the rule, and update_route_version publishes it: Rewrites can also be defined in vercel.json: Project-level rules live outside your deployment and are evaluated before its routes, so a published rule takes precedence over a vercel.json rewrite for the same path. Each surface fits a different workflow: How you define it Takes effect Best for CDN tab in the dashboard On publish Editing and testing rules visually Vercel CLI On publish One-off changes from the terminal vercel Python SDK or REST API On publish Automation and CI/CD vercel.json On each deployment Rewrites that ship with the application code Update Vercel CLI to the latest version and read the routing documentation to get started. Read more ## PyCharm & Django Fall Fundraiser DevFeed: [PyCharm & Django Fall Fundraiser]() Original publisher: [Read original article]() Author: Jeff Triplett Published: 2026-08-25T19:45:00Z Content type: news Language: en Sources: [The Django weblog]() Topics: [Django](), [PyCharm](), [ide](), [Python]() Tags: [collaboration](), [community](), [developers](), [django](), [events](), [framework](), [growth](), [onboarding](), [open-source](), [partnership](), [pycharm](), [python](), [support]() ### AI overview Django and JetBrains are running a fall fundraiser in which new or renewed PyCharm licenses are offered at a 30% discount, with JetBrains matching the contribution to the Django Software Foundation. The campaign supports Django maintenance, community programs, events, contributor onboarding, and the Foundation's planned Executive Director role. ### Source excerpt We are back with our friends at JetBrains for the second of the two "Buy PyCharm, Support Django" fundraisers we run together each year. Our spring campaign was the first. It remains one of the most impactful ways the community can support the Django Software Foundation. Your support of this campaign helps fund key initiatives such as: A Django Executive Director: Funding our first Executive Director, who will lead fundraising, operations, and community coordination for the Foundation. Django Fellows: Ensuring the rapid development and maintenance of Django. Django Girls: Making the Django community accessible to programming beginners around the world. International events and conferences: Supporting DjangoCons, one-day events, meetups, and other community gatherings around the world. Djangonaut Space: Onboarding new contributors to the Django project. The Executive Director role is new, which is why this campaign matters more than usual. The DSF raises around $300,000 a year today. Reaching $500,000 is what makes a full-time Executive Director sustainable, and campaigns like this one are how we close that gap. If leading that work sounds like you, applications are open until September 14, 2026. How the campaign works The campaign runs until September 10, 2026. When you buy a new PyCharm license or renew an existing one at a 30% discount through our special campaign link, JetBrains will donate an equal amount to the Django Software Foundation. You get a professional IDE that is trusted by Django developers worldwide, and the DSF receives a matched contribution. Get 30% off PyCharm, Support Django Thank you, JetBrains Beyond this campaign, JetBrains contributes to the Django ecosystem in ways that are easy to overlook but hard to overstate. The 2026 Django Developers Survey was published earlier this summer, and along with the Python Developers Survey, it gives the entire community a clearer picture of where Django and Python are heading each year. "JetBrains is one ## The Block and Tackle of Django's Code of Conduct Working Group DevFeed: [The Block and Tackle of Django's Code of Conduct Working Group]() Original publisher: [Read original article]() Author: Dan Ryan, Code of Conduct WG Chair Published: 2026-08-24T14:00:00Z Content type: article Language: en Sources: [The Django weblog]() Topics: [Django](), [Pull Request](), [Template]() Tags: [availability](), [community](), [diversity](), [django](), [framework](), [open-source](), [python]() ### AI overview Django's Code of Conduct Working Group explains the governance and technical process behind adopting Contributor Covenant 3.0, including membership, board oversight, escalation paths, decision-making, and structured proposals for future changes. ### Source excerpt In early 2026, Django's Code of Conduct Working Group adopted Contributor Covenant 3.0 as Django's Code of Conduct. I talked about why at DjangoCon US 2026 (slides here). That talk was mostly the story of how we managed the people side of the process. This post is the technical mechanics of how we managed the change and our work going forward. Who can change what, and who has to sign off The Code of Conduct Working Group is established by the DSF board and kept deliberately small. At least three people, per the working group manual, recruited for diversity of geography, background, and lived experience rather than just availability. Membership is volunteer and term-limited. Terms became annual in February 2026, and if a member doesn't respond to the January renewal check-in within a week, they're rolled off. Nobody has to feel guilty about stepping back. The board isn't a separate, distant approval layer sitting above the working group. The DSF board's president always holds a seat on the working group and acts as its board liaison. Other board members can volunteer alongside them, and two currently do, in addition to the chair. Day to day, the working group operates independently. It only has to go back to the board for three things: spending money, taking a drastic punitive action, or altering the Code of Conduct text itself. There's a second working group in the mix too. The Online Community Working Group handles routine moderation of Django's day-to-day spaces. It doesn't touch the Code of Conduct Working Group at all until something gets escalated: a formal report, a violation spanning multiple spaces, or an issue neither group can resolve alone. Each group appoints one of its own members as liaison to the other. If the two groups can't reach consensus on something that needs joint handling, either chair can send it to the board. Inside the working group itself, decisions are made by consensus first. If that doesn't happen, a two-thirds majority of members with ## DSF Office Hours DevFeed: [DSF Office Hours]() Original publisher: [Read original article]() Author: Jeff Triplett Published: 2026-08-12T17:25:24Z Content type: article Language: en Sources: [The Django weblog]() Topics: [Django](), [FIRST](), [GitHub]() Tags: [community](), [corporate](), [django](), [executive](), [framework](), [github](), [leadership](), [open-source](), [python]() ### AI overview The Django Software Foundation invites the Django community to join open office hours every Wednesday. The article highlights the Executive Director search, fundraising needs for the role, community participation, working groups, and ways for companies using Django to provide support. ### Source excerpt The DSF Board hosts open office hours every Wednesday at 6:00 PM UTC (check your local time). Anyone in the Django community is welcome to drop in. You do not need an agenda or an invitation. Video call details are on the DSF Office Hours page. We have been running these since October 2024, and right now we have two things we would especially like to talk with you about. Who shows up On any given Wednesday, you might find DSF Board members, Steering Council members, Django Fellows, working group members, and community members who are curious about joining a working group. There is no membership requirement. Anybody from the community can join, and often does. The Executive Director search We recently published a call for applicants for a Django Executive Director. If you are considering applying, or you are still deciding whether it is the right fit, come to office hours and ask us anything: what the job actually looks like, what we expect in the first year, how the search works. We would rather answer your questions directly than have you guess from a job posting. If this is the first you are hearing about the search, please help us spread the word. The best candidate may be someone who has not thought to look. Fundraising to support it Hiring an Executive Director is why we raised our 2026 fundraising goal from $300,000 to $500,000, which needs about $16,000 per month in additional recurring support. We have made real progress and are working to close the rest. If your company uses Django, you can help through corporate sponsorship, a direct donation, or GitHub Sponsors. Most of these are a small lift for a company that already depends on Django. If you want fundraising materials to bring to your leadership team, or help picking the option that fits, come to office hours, and we will get you what you need. Everything else Office hours cover plenty beyond that: what our working groups are up to and how to join one, projects the Foundation is working on, and whateve ## Porting Django to Go with AI Without the Naive Rewrite DevFeed: [Porting Django to Go with AI Without the Naive Rewrite]() Original publisher: [Read original article]() Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Django](), [Go Language](), [Artificial Intelligence](), [migration](), [Testing](), [test-coverage](), [Refactoring](), [proxy]() Tags: [ai](), [claude](), [copilot](), [django](), [go](), [migration](), [proxy](), [refactoring](), [test-coverage](), [testing]() ### AI overview The article argues that porting a Django API to Go with AI requires strong engineering foundations rather than line-by-line translation. It recommends tests, production-shaped traffic, clear module boundaries, code review, and incremental rollout mechanisms to establish behavioral parity and reduce migration risk. ### Source excerpt . [Porting Django to Go with AI Without the Naive Rewrite](porting-django-to-go-with-ai-cover... ## WebSocket support is now available for Python Functions DevFeed: [WebSocket support is now available for Python Functions]() Original publisher: [Read original article]() Author: Ricardo Gonzalez Published: 2026-07-23T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [WebSocket](), [Python](), [Vercel](), [ASGI](), [FastAPI](), [real-time](), [Django](), [Flask](), [Streaming](), [Frameworks](), [AI Chat](), [client]() Tags: [ai](), [applications](), [code](), [collaboration](), [communication](), [django](), [examples](), [features](), [flask](), [frameworks](), [python](), [real-time](), [server](), [streaming](), [vercel]() ### AI overview Vercel has added WebSocket support for Python applications and Functions. The feature supports bidirectional client-server communication for real-time use cases such as interactive AI streaming, chat, and multiplayer collaboration, with compatibility for ASGI and WSGI applications including FastAPI, Django, and Flask. ### Source excerpt Vercel now supports WebSocket connections for Python applications. WebSockets enable bidirectional communication between client- and server-side code, powering real-time features like interactive AI streaming, real-time chat, and multiplayer live collaboration. Both ASGI and WSGI applications are supported, including frameworks like FastAPI, Django, and Flask. Explore the FastAPI AI Chat and Flask AI Chat examples, or read the WebSockets documentation to get started. Read more ## Some more things about Django I've been enjoying DevFeed: [Some more things about Django I've been enjoying]() Original publisher: [Read original article]() Author: Julia Evans Published: 2026-07-21T00:00:00Z Content type: opinion Language: en Sources: [Julia Evans]() Topics: [Django](), [Back end](), [Databases](), [HTML](), [SQL](), [JavaScript](), [Gin](), [Python](), [Single-page application (SPA)](), [Vue.js]() Tags: [backend](), [database](), [django](), [flask](), [go](), [html](), [javascript](), [sql](), [vue]() ### AI overview The article shares the author's experience learning to build multi-page websites in a backend-focused style using Django, an SQL database, and server-rendered HTML. It discusses Django query sets and template filters, compares this approach with frontend-heavy JavaScript, Vue.js, Go, and Flask projects, and mentions some unresolved issues with Django. ### Source excerpt Hello! I'm on a funny journey right now where I'm trying to learn how to make websites in a sort of 2010 style, where I have an SQL database and render some HTML on the backend. It's kind of an interesting journey because it doesn't necessarily feel "easy" to me to make websites in this way: I never learned how to do it in the 2000s or 2010s, and there's a lot I need to learn. So here are some Django features that make building this kind of site feel more achievable than when I was trying and failing to use Go's standard library or Flask. And I'll talk about a couple of issues with Django I've run into. why learn to make websites like it's 2010? Previously the toolkit I felt confident with for making websites was: static site generators (like for this blog) static sites that do some fun stuff with Javascript (like this sql playground) simple Vue.js single page apps with either a Lambda as a backend or a Go backend (like mess with dns) I really liked this frontend-heavy approach for these super simple applications but when I started thinking about making something with a lot of different pages (instead of literally just one page), I didn't feel so excited about the options I saw that involved a lot of frontend code. So I figured I'd try the backend. Writing a backend-focused site that uses as little JS as possible feels the same to me in a way as writing a single-page JS website that does as little on the backend as possible, even though they might seem like opposites. In both cases I'm just trying to keep as much of the logic as possible in one place. Now for some thoughts about Django! I'm enjoying query builders I learned that I can define a "query set" class in Django with a bunch of methods with different WHERE statements I might want to use while constructing a query: Here's how I use it in my view code once I've defined what all the methods mean: Events.objects.approved() .for_tab(tab) .with_festivals(tab_params.festival_slugs) .is_free(tab_params.free) .is_ou ## The Real Python Podcast - Episode #303: Free-Threaded Python's History & uv in Production DevFeed: [The Real Python Podcast - Episode #303: Free-Threaded Python's History & uv in Production]() Original publisher: [Read original article]() Author: Real Python Published: 2026-07-17T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Python](), [Concurrent Programming](), [Concurrency](), [Wagtail](), [Django](), [Compiler](), [GitHub Copilot CLI](), [Model Context Protocol]() Tags: [article](), [cli](), [github-copilot](), [github-copilot-cli](), [locks](), [mcp](), [podcast](), [production](), [python](), [techniques]() ### AI overview This podcast episode discusses the history of attempts to remove Python's Global Interpreter Lock, the current free-threaded Python approach, and the challenges of running multiple tasks concurrently within one process. It also covers Python community news and projects, including JIT compiler work, GitHub Copilot CLI, MCP server testing, uv in production, Wagtail with Django, Python code quality, and thread-safety techniques. ### Source excerpt How many attempts have been made to remove Python's Global Interpreter Lock (GIL)? How do they compare to the current approach? Christopher Trudeau is back on the show this week with another batch of PyCoder's Weekly articles and projects. ## Learning a few things about running SQLite DevFeed: [Learning a few things about running SQLite]() Original publisher: [Read original article]() Author: Julia Evans Published: 2026-07-17T00:00:00Z Content type: article Language: en Sources: [Julia Evans]() Topics: [SQLite](), [Django](), [Object-relational mapping](), [Query (disambiguation)](), [Statistics]() Tags: [blog](), [django](), [orm](), [search](), [sqlite](), [statistics]() ### AI overview A personal account of operating SQLite in production for a small Django website. The article describes how running ANALYZE dramatically improved an SQLite FTS5 query and discusses the difficulty of cleaning up large numbers of rows without blocking other database writers. ### Source excerpt Hello! I've been working on a Django site recently, and I decided to use SQLite as the database. When I was getting started with using SQLite as database for a website I read a bunch of blog posts about how it is totally fine to use SQLite in production for a small site and I think it is totally fine, but what I did not fully appreciate is that SQLite is still a database, databases are complicated, and I do not know a lot about operating databases. So here are a couple of small things I've been learning about running SQLite. This is the 4th website I've used SQLite for, and I think this one is harder because with the power of the Django ORM I've been making the database do more work than I was previously without Django. I started by turning on WAL mode like all the blog posts said to do and hoping for the best. ANALYZE is apparently important Today I was running a query (using SQLite's FTS5 for full-text search) on a table with 4000 rows and it took 5 seconds. That seemed wrong to me: computers are fast! It turned out that what I needed to do was to run ANALYZE! Immediately the problem query went from taking 5 seconds to like 0.05 seconds (or some other number small enough that I didn't care to investigate further). I still don't know exactly what went wrong in the query plan, but my best guess is that it was some sort of accidentally quadratic thing. ANALYZE generates "statistics" (I guess about the number of rows in each table? and presumably other things?) so that the query planner can make better choices. Maybe one day I'll learn to read a query plan. cleaning up the database is tricky Occasionally I've run into situations where I accidentally put a bunch of rows in my database that I don't want to be there (for example completed tasks from django-tasks-db), and I want to clean them up. What's happened to me a few times in this case is: I run some kind of command to clean up the rows The command takes more than 5 seconds, since there are a lot of rows (though I ## Works on my machine: how we use AI to reproduce reported bugs DevFeed: [Works on my machine: how we use AI to reproduce reported bugs]() Original publisher: [Read original article]() Author: Neel Shah Published: 2026-06-08T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [Claude](), [SDKs](), [bug](), [Artificial Intelligence](), [Development](), [GitHub](), [Open Source](), [Python](), [Django](), [Boilerplate](), [Concurrency](), [legacy]() Tags: [ai](), [bugs](), [claude](), [concurrency](), [django](), [frameworks](), [github](), [legacy](), [open-source](), [python](), [sdks]() ### AI overview Sentry's SDK teams use a Claude skill to automate parts of reproducing reported bugs, including setting up boilerplate environments and playgrounds with the required parameters. The approach is intended to reduce triage time across the team's large SDK ecosystem. ### Source excerpt How Sentry's SDK team built a Claude skill to auto-reproduce bug reports, reducing triage time across 159 packages. ## Zero-configuration Django support DevFeed: [Zero-configuration Django support]() Original publisher: [Read original article]() Author: Marcos Grappeggia Published: 2026-04-09T15:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Django](), [Vercel](), [Python](), [Web](), [API](), [Command-line interface]() Tags: [api](), [cli](), [configuration](), [django](), [python](), [vercel](), [web]() ### AI overview Vercel now supports zero-configuration deployment for Django applications. Developers can deploy Django full-stack apps and APIs without redirects in vercel.json or use of the /api folder. Vercel serves static files through its CDN and uses Fluid compute with Active CPU pricing by default. ### Source excerpt Django, one of the most popular high-level Python web frameworks, for rapid development, is now supported with zero-configuration. You can now instantly deploy Django full-stack apps or APIs on Vercel. Vercel now recognizes and deeply understands the specifications of Django applications, removing the need for redirects in vercel.json or using the /api folder. All applications on Vercel use Fluid compute with Active CPU pricing by default. Static files will be served by the Vercel CDN. Deploy Django on Vercel or visit the Django on Vercel documentation Example Django app CLI entry point Project settings URL routing table Request handlers WSGI entry point Read more ## How to Add Payments to Your Django SaaS App with Dodo Payments DevFeed: [How to Add Payments to Your Django SaaS App with Dodo Payments]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-05T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Django](), [Software as a service](), [Python](), [SDKs]() Tags: [api](), [authentication](), [django](), [how-to](), [integration](), [license-keys](), [python](), [saas](), [subscriptions]() ### AI overview A step-by-step tutorial for integrating Dodo Payments into a Django SaaS application. It covers setting up the Python SDK, creating products and payment links, handling signed webhooks, managing subscriptions, and validating license keys. ### Source excerpt A step-by-step guide to integrating payments, subscriptions, and license keys into Django SaaS applications using Dodo Payments. ## NetBox Config Templates Tip: Query Objects Efficiently with .filter() DevFeed: [NetBox Config Templates Tip: Query Objects Efficiently with .filter()]() Original publisher: [Read original article]() Author: Rick Donato Published: 2026-03-10T08:00:07Z Content type: tutorial Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [NetBox](), [Django](), [Object-relational mapping]() Tags: [config](), [django](), [filter](), [interface](), [interfaces](), [netbox](), [orm](), [query](), [templates](), [tips]() ### AI overview A short tutorial showing how to use .filter() in NetBox Config Templates to query objects during lookups and conditional logic through the Django ORM QuerySet interface. ### Source excerpt Use .filter() in Config Templates to query objects during lookups and conditional logic. This exposes the Django ORM QuerySet filter directly in your templates. Here's an example: {% for iface in device.interfaces.filter(enabled=True, name__startswith="ge-") %} interface {{ iface.name }} {% endfor %} ## How to Integrate OAuth2 Into a Django/DRF Back End Without Losing Control DevFeed: [How to Integrate OAuth2 Into a Django/DRF Back End Without Losing Control]() Original publisher: [Read original article]() Author: Prachi Kothiyal Published: 2026-02-06T10:58:21Z Content type: tutorial Language: en Sources: [Backend Archives | Talent500 blog]() Topics: [Django](), [OAuth 2.0](), [Back end](), [Authentication](), [API](), [Framework]() Tags: [a-minimal-view-for-token-exchange](), [api](), [authentication](), [back-end](), [backend](), [configuring-back-end-authentication](), [django](), [newsletters](), [oauth2](), [rest](), [server-side-vs-client-side-oauth2-flows](), [testing-and-reliability-considerations](), [what-the-back-end-needs-to-do](), [why-rely-on-a-social-auth-library]() ### AI overview A practical guide to integrating OAuth2 social login into a Django or Django REST Framework back end. It recommends letting the front end handle the provider flow while the back end validates third-party tokens, maps social identities to local accounts, and issues API credentials. ### Source excerpt When a Django or Django REST Framework (DRF) back end is already handling authentication, adding "Log in with Google" or [...] The post How to Integrate OAuth2 Into a Django/DRF Back End Without Losing Control appeared first on Talent500 blog. ## Some notes on starting to use Django DevFeed: [Some notes on starting to use Django]() Original publisher: [Read original article]() Author: Julia Evans Published: 2026-01-27T00:00:00Z Content type: article Language: en Sources: [Julia Evans]() Topics: [Django](), [Framework](), [Object-relational mapping](), [Website](), [Database](), [Rails](), [Laravel]() Tags: [database](), [django](), [framework](), [laravel](), [orm](), [rails](), [web]() ### AI overview A developer shares notes from starting to use Django after previously trying Rails. They find Django's explicit project structure easier to return to after long breaks, appreciate its built-in and customizable admin interface, and are enjoying its ORM for expressing database relationships and queries with less code. ### Source excerpt Hello! One of my favourite things is starting to learn an Old Boring Technology that I've never tried before but that has been around for 20+ years. It feels really good when every problem I'm ever going to have has been solved already 1000 times and I can just get stuff done easily. I've thought it would be cool to learn a popular web framework like Rails or Django or Laravel for a long time, but I'd never really managed to make it happen. But I started learning Django to make a website a few months back, I've been liking it so far, and here are a few quick notes! less magic than Rails I spent some time trying to learn Rails in 2020, and while it was cool and I really wanted to like Rails (the Ruby community is great!), I found that if I left my Rails project alone for months, when I came back to it it was hard for me to remember how to get anything done because (for example) if it says resources :topics in your routes.rb, on its own that doesn't tell you where the topics routes are configured, you need to remember or look up the convention. Being able to abandon a project for months or years and then come back to it is really important to me (that's how all my projects work!), and Django feels easier to me because things are more explicit. In my small Django project it feels like I just have 5 main files (other than the settings files): urls.py, models.py, views.py, admin.py, and tests.py, and if I want to know where something else is (like an HTML template) is then it's usually explicitly referenced from one of those files. a built-in admin For this project I wanted to have an admin interface to manually edit or view some of the data in the database. Django has a really nice built-in admin interface, and I can customize it with just a little bit of code. For example, here's part of one of my admin classes, which sets up which fields to display in the "list" view, which field to search on, and how to order them by default. @admin.register(Zine) class ZineAdmin(adm ## Moving from Django DRF to Ninja API / Pydantic DevFeed: [Moving from Django DRF to Ninja API / Pydantic]() Original publisher: [Read original article]() Author: Michael Sidharta Published: 2025-11-10T05:35:43Z Content type: comparison Language: en Sources: [Kogan.com]() Topics: [Django](), [Pydantic](), [API](), [Python](), [Development](), [OpenAPI Specification](), [Swagger]() Tags: [api-documentation](), [data-validation](), [django](), [fastapi](), [python](), [swagger]() ### AI overview This article examines moving from Django REST Framework API patterns to Django Ninja API and Pydantic. It describes motivations including reducing boilerplate, improving performance for some use cases, using modern Python type hints and data validation, and enhancing developer experience. It also outlines Django Ninja's type-based validation, automatic OpenAPI documentation, performance focus, and simplified endpoint definitions. ### Source excerpt As our project grows, we're always looking for ways to streamline development, improve performance, and enhance the developer experience. Recently, we've been exploring a shift from our traditional Django REST Framework (DRF) API patterns to a combination of Django Ninja API and Pydantic. This blog post will delve into our motivations for this change, the benefits we've observed, and some considerations for others contemplating a similar transition. Why Consider a Change from Django DRF? Django REST Framework has been a robust and widely adopted solution for building APIs with Django. It provides a comprehensive set of tools, including serializers, viewsets, and excellent browser-based API interfaces. However, as our needs evolved, we identified areas where a different approach could offer advantages: Boilerplate Code: While DRF offers powerful abstractions, creating serializers, views, and viewsets can sometimes lead to a significant amount of boilerplate code, especially for simpler APIs. Performance: For certain use cases, the overhead of DRF's serializer validation and rendering can impact performance, particularly in high-throughput scenarios. Modern Python Features: We were keen to leverage modern Python features like type hints and data validation more extensively, which are core to Pydantic. Developer Experience: A more concise and explicit way to define API endpoints and data structures could improve developer productivity and reduce potential errors. Introducing Django Ninja API and PydanticDjango Ninja API Django Ninja is a web framework for building APIs with Django and Python 3.6+ type hints. It's heavily inspired by FastAPI and offers a number of compelling features: Type Hinting for API Endpoints: You define your request and response models using Pydantic, and Ninja automatically validates and serializes the data based on these type hints. Automatic OpenAPI (Swagger) Documentation: Just like FastAPI, Ninja generates interactive API documentation out o ## Reliable Django Signals DevFeed: [Reliable Django Signals]() Original publisher: [Read original article]() Author: Haki Benita Published: 2025-10-29T22:00:00Z Content type: tutorial Language: en Sources: [Haki Benita]() Topics: [Django](), [implementation](), [modules]() Tags: [articles](), [decoupling](), [django](), [implementation](), [modules]() ### AI overview This article explains that Django signals can be unreliable because of their underlying transport. It presents an alternative transport implementation using background tasks to make signals more reliable and safer for mission-critical workflows. ### Source excerpt Django signals are extremely useful for decoupling modules and implementing complicated workflows. However, the underlying transport for signals makes them unreliable and subject to unexpected failures.In this article, I present an alternative transport implementation for Django signals using background tasks which makes them reliable and safer to use in mission critical workflows. [Next page]()