Good point, I suppose it'll be better if it were in forms. I'll be looking
into this.
On Sunday, January 24, 2016 at 4:14:22 AM UTC+11, Tim Graham wrote:
>
> For a quick glance, the high-level idea looks okay (subject to a
> deprecation path, of course), however, in my mind it would be more usef
Triaged
---
https://code.djangoproject.com/ticket/26096 - Django 1.9.1 fails to delete
an existing test database on PostgreSQL and MySQL (fixed)
https://code.djangoproject.com/ticket/26097 - UserCreationForm isn't using
password_validators_help_text_html (accepted)
https://code.djangopr
For a quick glance, the high-level idea looks okay (subject to a
deprecation path, of course), however, in my mind it would be more useful
to try to move toward enhancing the forms library itself (if possible) so
that less admin-specific code is needed. Have you thought about this at all?
On Sa
Currently the BaseModelAdmin class has a method called
formfield_for_dbfield which has a conditional block that in turn calls
different formfield_for_* methods depending on the type of database field
it is handling. In order to do any custom logic to these fields we need to
override these metho
