As always, depends. Just think about how source control (i.e. code ownership), re-usability and IDE integration/navigation would fit with each approach. Contrary to Russ, I have my form classes near to my view functions, but I won't bet my C++ Builder 4 CD that its the best way :)
Probably not an issue, but if you import as: from django import newforms as forms you may want to watch out for namespace issues. -rob On May 25, 5:58 pm, ringemup <[EMAIL PROTECTED]> wrote: > Obviously, this doesn't *really* matter, but I'm looking for best > practices: > > Where would you recommend putting the code for a custom form class? > In views.py? In models.py? In a separate forms.py? > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
