Thanks alot @BugBytes for this video. I have been waiting for this since the release of Django 5. Amazing features. The Django community keeps making me fall more in love with Django with each new released features. And they make things so simple and straightforward. Thanks to the Django community out there, I really appreciate your efforts and hardwork. 😊
I really like this kind of tutorials I didnt see a lot of content that reads the official django documentaion and explains each section so brief but informative (maybe I didn't look enough ) thank you please create more content like this
Great explanation, just subscribed :) What about CBV and the decorator `login_not_required`? The docs does not explicitly tell the solution for such case or am I missing something?
Can someone test 'LoginRequiredMiddleware' be used django all-auth? I might be a unique case, but with django all-auth and the LOGIN_URL set get the thing redirecting like crazy and I get ERR_TOO_MANY_REDIRECTS . Most likely just me but would love feedback. Thanks
Connection pooling in SA is across all SQL dialects, for example. Django ORM just now got it and only for postgresql. Little things like, showing an executing query in SA is easy, just enable echo=True in the engine definition. In Django you have to jump through hoops in the logging settings or install silk. Union, complex joins in SA are a lot more intuitive than Annotate. The downside in SA there is no built-in version control, you have to use alembic
@@Yarkanlaki nop they mostly holding lots of meetings to work on a feature or fix and it takes a lot of voting and so on for them to finally agree on something. there is a foundation behind Django and Python that's why things move so slowly and there is barely any marketing for this platform.
I can understand why you could see things this way and I really can’t black and white agree/disagree. However, if you are open to it, may I kindly add to your post, offer another viewpoint and sprinkle in some grey to what is often presented as a black/white argument!? I think the perception that Django is ‘slow’ to adopt new features is largely born from the fact that it is a robust, battery’s included web framework where most of the ‘new’ stuff is already enterprise battle tested and proven at scale and has been for a long time with big enterprises - templates, request management, form validation, a robust user permisioning model, ORM, etc.. this isn’t exciting new stuff for Django but very important when building a robust enterprise app. Django has been around for quite a while and evolved a LOT. Out of box it gives you a LOT of enterprise grade capabilities that you take for granted until you go looking for an equivalent on another framework e.g. picking a router or a robust ORM, test integration etc… Django as a project, culturally tries not to be bleeding edge but instead prefers to be leading edge - this is a philosophy that serves developers who use it well. Generally speaking when you build an app, you can sleep easy that an updated version of Django is not going to break your app. Things don’t break because of a new fad and some new capability being rushed out the door. Changes are considered (even debated :D ). When the framework already caters very well to most of the ‘boring’ stuff it can create a perception that it is slow/dated to adopt new. I do think that slowness to adopt (rewrite) portions of the codebase to Async may have fed that perception of slowness. Similarly the Django Template Library is only relatively recently getting a second life with HTMX, Alpine.JS. However it’s this flexibility also that you can use Django as an API layer and use it with a React front-end or Angular front-end that is also one of it’s strengths. If we look at more recent exercises such as partial page refreshes, django template partials and embracing noJS frameworks like Alpine.js and HTMX, I think that arguably the Django community is embracing change very well and the front end (presentation layer which I feel was Djangos weakest area) is now becoming very strong again. Just my 0.02. Happy developing you guys and hope that whatever you’re using to build with that you are enjoying :)
hi i have register, login and dash pages i make LoginRequired on my dash when i enter to dash by ulr it goes to login but when i make login i kept in the login page is not going to dash and get this url [23/Aug/2024 00:28:00] "GET /pages/login?next=/pages/dash HTTP/1.1" 200 10805 , the ulr and the view all is correct can u help me with this ? why i kept in login page and how to fix it
Thanks alot @BugBytes for this video. I have been waiting for this since the release of Django 5.
Amazing features. The Django community keeps making me fall more in love with Django with each new released features. And they make things so simple and straightforward. Thanks to the Django community out there, I really appreciate your efforts and hardwork. 😊
yes Plz we want All changes in Django5 to be covered, the "before" and "after" method u doing is really great.
Thank you, glad you like that approach!
awesome as always
@@mrmuranga thank you!
Thank you, I wish you could upload more material of Django, I leave like and sub
Thanks a lot!
thank you for covering this!
Thanks for watching!
I really like this kind of tutorials I didnt see a lot of content that reads the official django documentaion
and explains each section so brief but informative (maybe I didn't look enough )
thank you please create more content like this
Thanks a lot! I'll try and create more videos in this style.
Great explanation, just subscribed :) What about CBV and the decorator `login_not_required`? The docs does not explicitly tell the solution for such case or am I missing something?
I love this style of videos, thank you
Thanks a lot!
Make a video on Django react crud operation with login sign up auth
Nice
I like the tutorial most
Thanks a lot!
good thank
Thanks!
Neat
Thanks 🎉❤
Thanks for watching!
Can someone test 'LoginRequiredMiddleware' be used django all-auth? I might be a unique case, but with django all-auth and the LOGIN_URL set get the thing redirecting like crazy and I get ERR_TOO_MANY_REDIRECTS .
Most likely just me but would love feedback.
Thanks
I want Django to natively support sqlalchemy. As much as I like Django ORM SA is just miles above it
That's interesting - I've heard mixed opinions on this. I do like both pretty equally, personally.
Connection pooling in SA is across all SQL dialects, for example. Django ORM just now got it and only for postgresql. Little things like, showing an executing query in SA is easy, just enable echo=True in the engine definition. In Django you have to jump through hoops in the logging settings or install silk.
Union, complex joins in SA are a lot more intuitive than Annotate. The downside in SA there is no built-in version control, you have to use alembic
Can you do sorting on user__username ?
I feel like Django moving way too slow compare to other frameworks like Laravel and Next.js
It seems Django conts are busy with fixing alot of bugs until they stabilize it and then add new futures
@@Yarkanlaki nop they mostly holding lots of meetings to work on a feature or fix and it takes a lot of voting and so on for them to finally agree on something. there is a foundation behind Django and Python that's why things move so slowly and there is barely any marketing for this platform.
Interesting perspective, I definitely agree to a point.
I can understand why you could see things this way and I really can’t black and white agree/disagree. However, if you are open to it, may I kindly add to your post, offer another viewpoint and sprinkle in some grey to what is often presented as a black/white argument!?
I think the perception that Django is ‘slow’ to adopt new features is largely born from the fact that it is a robust, battery’s included web framework where most of the ‘new’ stuff is already enterprise battle tested and proven at scale and has been for a long time with big enterprises - templates, request management, form validation, a robust user permisioning model, ORM, etc.. this isn’t exciting new stuff for Django but very important when building a robust enterprise app.
Django has been around for quite a while and evolved a LOT. Out of box it gives you a LOT of enterprise grade capabilities that you take for granted until you go looking for an equivalent on another framework e.g. picking a router or a robust ORM, test integration etc…
Django as a project, culturally tries not to be bleeding edge but instead prefers to be leading edge - this is a philosophy that serves developers who use it well. Generally speaking when you build an app, you can sleep easy that an updated version of Django is not going to break your app. Things don’t break because of a new fad and some new capability being rushed out the door. Changes are considered (even debated :D ).
When the framework already caters very well to most of the ‘boring’ stuff it can create a perception that it is slow/dated to adopt new. I do think that slowness to adopt (rewrite) portions of the codebase to Async may have fed that perception of slowness. Similarly the Django Template Library is only relatively recently getting a second life with HTMX, Alpine.JS. However it’s this flexibility also that you can use Django as an API layer and use it with a React front-end or Angular front-end that is also one of it’s strengths.
If we look at more recent exercises such as partial page refreshes, django template partials and embracing noJS frameworks like Alpine.js and HTMX, I think that arguably the Django community is embracing change very well and the front end (presentation layer which I feel was Djangos weakest area) is now becoming very strong again. Just my 0.02.
Happy developing you guys and hope that whatever you’re using to build with that you are enjoying :)
If anything, I would be enraged if Django became anything like laravel. It's a clusterfuck of over engineered shit, deprecating as it releases...
list_display = ["foreign_field__field",] :D :D :D
pip install django == 4.2
hi i have register, login and dash pages i make LoginRequired on my dash when i enter to dash by ulr it goes to login but when i make login i kept in the login page is not going to dash and get this url [23/Aug/2024 00:28:00] "GET /pages/login?next=/pages/dash HTTP/1.1" 200 10805 , the ulr and the view all is correct can u help me with this ? why i kept in login page and how to fix it
@@MahmoudDuhaidi you would need to post some code, perhaps someone can help, it sounds like the login view is not correctly authenticating users