Django 1.7 makemigrations fails when specifying a default value about django-enumfields HOT 11 CLOSED

Which version are you using? 0.5.1 contains #19 which may have fixed this.

from django-enumfields.

Using django-enumfields==0.5.1 and Django==1.7

from django-enumfields.

Hm, alright. I'll try to look into this later this week. At the moment, the tests aren't running with Django 1.7 because of the app loading changes so that'll probably have to come first.

from django-enumfields.

I believe this will help helpful:
https://code.djangoproject.com/ticket/22951

I updated to 1.7.1 and still have problems, perhaps because the check for 'type' added in Django 1.7.1 fails for django-enumfield's enum class. I will have to investigate more.

from django-enumfields.

This is how I solved the issue, including a workaround for 22961:

class DeconstructableEnum(Enum):
    def __init__(self, *args, **kwargs):
        super(DeconstructableEnum, self).__init__(*args, **kwargs)
        # migrations are able to serialize the class natively, but not instances
        self.deconstruct = lambda: ('%s.%s' % (self.__module__, self.__class__.__name__), [self.value], {})

from django-enumfields.

@gavinwahl Oh, that's clever! Are there any drawbacks to doing that?

from django-enumfields.

It's kind of hacky and confusing. Depending on whether a fix is released in Django, we might not need a workaround at all. I opened https://code.djangoproject.com/ticket/23950 for this issue.

If it doesn't end up getting fixed in Django and getting released in 1.7.2, I don't see a drawback to doing this workaround in django-enumfields.

from django-enumfields.

👍 If you want to submit a PR, I'll merge it.

from django-enumfields.

The Django bug was fixed and backported to 1.7.x so we can add a normal deconstruct method without any workaround.

from django-enumfields.

Oh cool. Does that mean we're good to close this?

from django-enumfields.

Using a bleeding edge Django (with the supposedly fixing commit dee4d23f7e703aec2d1244e4facbf7f4c88deed5 included) did not fix the problem for me. (Same error.)

However, the first commit in the referenced PR (#24) does fix this, by serializing the default kwarg as the enum's underlying value. Comments appreciated :-)

from django-enumfields.