Thanks for the ideas, guys! Looks to me like forms.py will do the
trick for now.
--~--~-~--~~~---~--~~
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.
On 27-May-07, at 9:18 AM, SmileyChris wrote:
> That's why, like Russ, I also use a forms.py file and do the newforms
> import like:
> from django.newforms import *
i import django.newforms as nforms - so i can use both new and old
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshel
On May 26, 2:53 pm, oggie rob <[EMAIL PROTECTED]> wrote:
> Probably not an issue, but if you import as:
> from django import newforms as forms
> you may want to watch out for namespace issues.
That's why, like Russ, I also use a forms.py file and do the newforms
import like:
from django.newforms
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
On 5/26/07, 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?
Personally, I've been putting forms in
5 matches
Mail list logo
