I'd be -1 on the change here too. That QuerySet shows you its value in the shell is beyond valuable.
Look at the Django Tutorial <https://docs.djangoproject.com/en/2.2/intro/tutorial02/#playing-with-the-api>, or the Django Girl Tutorial <https://tutorial.djangogirls.org/en/django_orm/>, or any of the other learning examples, and imagine making it so that these *playing with the API* examples required grasping *at which point QuerySets are evaluated*. Users don't get that quickly. (These exact issues come up all the time on DRF — Why isn't my QuerySet updating? Because you evaluated it in your class definition...) If you must have a different behaviour here, use a subclass. Kind Regards, Carlton On Tuesday, 15 October 2019 10:21:14 UTC+2, Mariusz Felisiak wrote: > > I'm -1 to this change. ... to be honest even with all of this fetching the > first 20 rows should not crash your production database... I'm against this > change because it will have a negative impact for most of users ...It will > also have a big impact on our documentation ~ 200 examples to change. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e6c631ea-d0b0-4d39-a784-2169f1445952%40googlegroups.com.
