Hi folks, I'm just starting to play with django-registration and I want to subclass the RegistrationForm for a couple of cosmetic tweaks (capitalising the labels on the fields -- there may be a simpler way to do this, but indulge me for the purposes of this question). I understand that subclassing RegistrationForm and reassigning the label strings is the way to do this -- no problem.
My question is where to *put* that subclass. I can think of a few places: - the project itself - an "overrides" app dedicated to holding overrides for external apps - a "registration_overrides" app dedicated to holding overrides for just that one external app Perhaps there are other ways. Of these, I'm favouring #2. While #3 has the virtue of being more portable, it seems like a lot of (logical) overhead to perform a simple modification to another app. So I guess I'd like to hear if there's an accepted way to do this, or failing that, what anyone has found to work well (or what to avoid). Thanks all, Scott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
