42
No such thing exists. That’s why the default
and default_if_none
filters exist. This is a feature; it makes you think about what you’re doing instead of relying on some behavior that would often times be misleading. If there’s a potential for a variable to be None
, then you should plan for that contingency. If the variable should always have some value, then the "None" indicates something is not right. If the default was to just render a blank string, then you would not know whether the value is not defined or is actually a blank string. Write coherent code and forget about shortcuts.
4
“Explicit is better than implicit”
Think of how enraged you would be when things wouldn’t render properly because you forgot that you had enabled the magic “render everything with a false value as a null string” setting.
If you find you’re using the default_if_none
filter a lot, you might want to consider changing casting None
to ''
BEFORE it’s passed to the template.
Your template will be simpler, and you will have explicitly made this decision to stringify null values.
- [Django]-How to set environment variables in PyCharm?
- [Django]-How to dynamically set the queryset of a models.ModelChoiceField on a forms.Form subclass
- [Django]-Can you migrate backwards to before the first migration in South?
4
This should do the trick, put it somewhere in the initialization code, for eg. in wsgi.py
# Patch template Variable to output empty string for None values
from django.template.base import Variable
_resolve_lookup = Variable._resolve_lookup
def new_resolve_lookup(self, *args, **kwargs):
o = _resolve_lookup(self, *args, **kwargs)
return o or u""
Variable._resolve_lookup = new_resolve_lookup
- [Django]-Disable link to edit object in django's admin (display list only)?
- [Django]-How to verify if object exist in manytomany
- [Django]-More than 1 foreign key