Just make a deconstructible subclass and use it instead.
from django.utils.deconstruct import deconstructible
The basic issue here is that you are trying to use Django 1.7 with a package (
django-storages) that doesn’t appear to have been updated to work with that version yet.
Here are some excerpts from the documentation to explain what is happening:
Migrations are just Python files containing the old definitions of your models – thus, to write them, Django must take the current state of your models and serialize them out into a file.
While Django can serialize most things, there are some things that we just can’t serialize out into a valid Python representation – there’s no Python standard for how a value can be turned back into code.
You can let Django serialize your own custom class instances by giving the class a deconstruct() method.
So the solution here is to give the class
deconstruct() method. That will probably be as easy as applying the
@deconstructible class decorator.
Presumably the package will incorporate this change at some point (or perhaps the master branch already has it?), but you could also just patch it yourself.
- TemplateDoesNotExist at / base.html
- How to write a Django view for a POST request
- Django annotating with a first element of a related queryset