I really, really like the django_enum package.
Imagine Django's TextChoices/IntegerChoices classes, but with the ability to encapsulate any additional information for each choice in one place.
I don't use it everywhere, but it's super useful in a number of use-cases.
Here are a few places where I've found django_enum makes things easier. See alt text for more detail about how I use of each of these.
Check it out: https://django-enum.readthedocs.io/en/stable/
And follow: @bckohan
@jonathanbiemond @bckohan Mainly cases where the data is unlikely to change much in the future & is more "fact" than something I might make adjustments to regularly.
For instance, each field in my Terminology model covers pretty much every term variation that I've found in literature or in practice. It's sort of one-and-done.
Likewise, while new linings may be developed over time for waterways, it's unlikely they will be in common use anytime soon, and I've covered most existing cases.
Jack Linke 🦄
Adam Johnson 
Jonathan Biemond
Brian Kohan
✨ Emma 🐍 🎸 🐹