My favourite workaround for this is to register a small dummy apps
overriding default properties:
from django.conf import settings
if "django.contrib.auth" in settings.INSTALLED_APPS:
# modify User model properties only if contrib.auth is installed
from django.contrib.auth.models import User
#
Regarding Russ' comment on pluralization:
Option 1: Spend a lifetime trying to make a single tag that can
accommodate every possible pluralization rule scheme
Option 2: Provide a simple implementation that works for a lot of
cases, and encourage others to write specific template tags for thei
A word of caution on dropping support of python 2.4: it is still shipped
with RHEL 5 which is supported until 2014
(http://www.redhat.com/security/updates/errata/).
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
> However, the bigger issue is that I think changing the definition of
> this field really requires a migration mechanism (which would update
> existing databases), which we don't have. We really don't want the
> situation of bugs which are impossible to reproduce because they
> depend on installat
