yes the problem using this method is that DRY principle is broken,
because you redefine the fields that are already defined
I was thinking of MixIn the 2 Forms to keep the whole thing reusable
but nevermind, if this is the only way, I'll do it like this.
thanks
On Tue, Jun 2, 2009 at 05:57, Risha
On Tue, Jun 2, 2009 at 9:10 AM, Marco Bazzani wrote:
>
> On Mon, Jun 1, 2009 at 23:19, V wrote:
> >
> > On Jun 1, 6:50 pm, Marco Bazzani wrote:
> >> I'm trying to extends django-registration app with some more fields in
> >> the moment of registration
> >> those fields are saved in a subclass of
On Mon, Jun 1, 2009 at 23:19, V wrote:
>
> On Jun 1, 6:50 pm, Marco Bazzani wrote:
>> I'm trying to extends django-registration app with some more fields in
>> the moment of registration
>> those fields are saved in a subclass of User
>>
>> for reference here are the form
>> classes:http://bitb
On Jun 1, 6:50 pm, Marco Bazzani wrote:
> I'm trying to extends django-registration app with some more fields in
> the moment of registration
> those fields are saved in a subclass of User
>
> for reference here are the form
> classes:http://bitbucket.org/ubernostrum/django-registration/src/tip/
I'm trying to extends django-registration app with some more fields in
the moment of registration
those fields are saved in a subclass of User
for reference here are the form classes:
http://bitbucket.org/ubernostrum/django-registration/src/tip/registration/forms.py#cl-21
ok here is my code
#mo
5 matches
Mail list logo
