Color field is not displayed correctly in the admin about django-colorinput HOT 3 OPEN

Looks like this is set globally per field-type in django.contrib.admin.options:

FORMFIELD_FOR_DBFIELD_DEFAULTS = {
    …
    models.CharField: {'widget': widgets.AdminTextInputWidget},
    …

(cf. source)

It's meant to be overridden via ModelAdmin.formfield_overrides - not sure much can be done at the form field level, which is where this package's code lives...

from django-colorinput.

FWIW, I got it to work by directly hacking it into that file in my local virtualenv's django installation:

from colorinput.models import ColorField
from colorinput.forms.widgets import ColorInputWidget
…
FORMFIELD_FOR_DBFIELD_DEFAULTS = {
    …
    ColorField: {'widget': ColorInputWidget},
}

… so it is possible.

Now the question becomes whether monkey-patching that dict from my reusable app code is possible, safe, robust and a good idea (or even: sane).

from django-colorinput.

I tried simply doing

import django.contrib.admin
from django.contrib.admin.options import FORMFIELD_FOR_DBFIELD_DEFAULTS

…

FORMFIELD_FOR_DBFIELD_DEFAULTS[ColorField] = {'widget': ColorInputWidget}

in colorinput/forms/fields.py and it doesn't work.

Is it because this runs at import time, or does import FORMFIELD_… provide my module's namespace with its own copy of this dict somehow, or is it a third thing (e.g some kind of race condition)?

Either way, this simple approach doesn't work and even if it did: I'm far from sure this is such a good idea. Seems like a pretty dirty hack to me.

In the worst case, I'll just have to document how to fix this through a custom ModelAdmin class with formfield_overrides so users can do that in their own projects, if it bothers them.

from django-colorinput.