Hi Jamesie,
I recently proposed adding a post_init signal for forms
(https://groups.google.com/forum/#!topic/django-developers/SviNiWy3Bjc).
Here's an example of how you might adjust the
forms:
https://github.com/seddonym/formsignals/blob/master/formsignals/priority/receivers.py
If such a
Hi JP,
That's a good point, sorry I didn't make it clear.
The fork is installed from within the requirements file but you can also
see it here, on the ticket_27923
branch: https://github.com/seddonym/django/tree/ticket_27923
I've updated the README to help.
I'd be interested to hear if
Hi Jainesh,
Have a look at this page which should give you an idea about where to
start:
https://docs.djangoproject.com/en/1.10/intro/contributing/#finding-your-first-real-ticket
On Monday, 13 March 2017 13:52:34 UTC, Jainesh Patel wrote:
>
> Hello,
>
> I am a final year CSE student from PICT,
ould value any comments!
On Monday, 6 March 2017 19:08:29 UTC, David Seddon wrote:
>
> Hi all,
>
> One thing I've always found challenging with Django is to adjust the
> functionality of forms from other apps. An example might be to add an
> extra field to a login form prov
:18:26 Melvyn Sopacua wrote:
>
> > On Monday 06 March 2017 10:10:41 David Seddon wrote:
>
> > > Hi all,
>
> > >
>
> > > One thing I've always found challenging with Django is to adjust the
>
> > > functionality of forms from other apps. An
I totally agree that signals are open to misuse, and I take your points.
Inexperienced developers often seem to use them just because they're
there, rather than to encapsulate their apps and avoid circular
dependencies. The Django signals documentation could probably do with a
bit more
Hi all,
One thing I've always found challenging with Django is to adjust the
functionality of forms from other apps. An example might be to add an
extra field to a login form provided by a third party module.
What I end up doing is often overriding the urlconf, view and form class.
Or,
