News for hackers. Stuff that matters.
Re:Harmful Defaults in Django by jmconfuzeus on Friday January 07, 2022 @12:12PM (#29841694)
It's highly unlikely that will you execute unnecessary queries from view code because usually you'll have a context like {"pizzas": page_obj.object_list}. You'll almost never execute something like:

  for pizza in pizzas:
      print(pizza.topping.name)
But you'll certainly do the following in templates:

  {% for pizza in pizzas %}
    <p>{{ pizza.topping.name }}</p>
  {% endfor %}
I also don't understand why you want to avoid 3rd party packages, especially if it helps you write better code.
Re:Harmful Defaults in Django by Nextgrid on Sunday January 09, 2022 @03:07AM (#29861330)
My argument was that the third-party package is what's key here. Merely converting your querysets to a list in code before handing it off to the template won't fully protect you against extra queries.

I'm not necessarily trying to avoid third-party packages, in fact I've installed the package you suggested in one of my projects and will be trying it out.