Fork me on GitHub
Django (anti)patterns

    Antipatterns

    1. A GET request with side-effects
    2. A model with a …Model suffix
    3. Chaining querysets together
    4. Checking ownership through the UserPassesTestMixin
    5. Constructing a new form when validation fails
    6. Fetching the logged in user with a query
    7. Filtering in the template
    8. Foreign key with _id suffix
    9. Giving related_name=… the same name as the relation
    10. Manually constructing a slug
    11. Modifying slugs and primary keys of model objects
    12. (Over)use of .values()
    13. Passing parameters directly in the query string of a URL
    14. Plural model class names
    15. Refer to the User model directly
    16. Rendering content after a successful POST request
    17. Return a JsonResponse with safe=False
    18. Signals
    19. Use datetime.now as default=… for a created_on field
    20. Use .get(…) to retrieve the object in a view
    21. Using a FloatField for money
    22. Using commit=False when altering the instance in a ModelForm
    23. Using len(…) on a QuerySet with no further use
    24. Using request.POST or None

    Patterns

    1. Annotate a condition as BooleanField
    2. Set values to a created/updated object in a class-based view

    Troubleshooting

    1. Can not extract/filter a Date(Time)Field when time zones are enabled