r/django 19h ago

I'm Starting a Daily Django Errors Series – Follow Along! ⭐

15 Upvotes

I'm starting a new Django series where I'll post one common Django error every day and walk through how to fix it with a simple, beginner-friendly explanation.

Whether you're just getting started or you've been building with Django for a while, I hope these posts help you debug your projects a little faster.

Feel free to follow along, ask questions, and even suggest errors you'd like me to cover next. Happy coding! 🚀


r/django 21m ago

Django 6.1 release candidate 1 released

Thumbnail djangoproject.com
Upvotes

r/django 47m ago

The Value of Experience: Building Skills That Command Respect(wrote this back last year on devto)

Thumbnail
Upvotes

r/django 8h ago

Hosting and deployment fymo: server-rendered Svelte 5 from Python

1 Upvotes

When in my beginner days, every side project started the same way.. it's usually, that Django or DRF on one side, a Svelte app on the other, and a weekend gone on wiring auth, CORS and two deploys before writing a single actual feature. like, for work-scale projects, fair enough. but for small and medium projects, like mine, solo ones, that was always more hassle than the project itself. so back in August 2022 I started a project called fymo, to make one-repo Python+Svelte projects a normal thing to build.

I got stuck early, compiling Svelte from Python and making the two sides talk to each other was beyond me then, so it sat there for a while, like my other side projects did. between years, i came back and forth, but this time it stuck, and I finished it.

fymo renders real Svelte 5 components from Python stuff like; esbuild compiles them at build time, one long-lived Node process does the SSR, and the browser hydrates them like any Svelte app.

day to day it'll feel familiar: controllers are basically views that return a dict, and the dict lands in Svelte as props. functions under app/remote/ become typed imports in Svelte, so no serializer, no endpoint, no fetch code. fymo new gives a running app with sign in, fymo generate resource posts gives a routed page, CRUD endpoints and a passing test file. fymo destroy takes it back out, unless you edited the files, then it refuses.

Anything misconfigured fails at boot with the fix right there in the error message. Nothing falls back silently. that's most of the design philosophy really.

But to be clear, it's not Django and it's not trying to be. no ORM, no admin, no forms, bring your own data layer. if you need those, Django is still the right call. this is for when Django plus DRF plus a separate frontend repo felt like three tools for a one-tool job.

But limitations, honestly: you need Node installed (build and runtime), it's WSGI not asyncio, no ORM, one maintainer, and it's v0.20 so things still break between versions, loudly though.

Repo: https://github.com/Bishwas-py/fymo pip install fymo

I'd honestly like to hear where it breaks, unusual project shapes are exactly what I can't simulate on my own.


r/django 19h ago

Django Errors

Post image
0 Upvotes

🚨 Django Error #001

Debugging is part of every developer's journey. In this series, I'll be sharing common Django errors I've encountered, why they happen, and how to fix them.

Today's error: RelatedManager Object Has No Attribute.

I hope this saves someone hours of debugging! 💚

💬 Have you ever encountered this error? Let me know in the comments.

💾 Save this post for later and follow for more Django Errors & Solutions.