#22337: makemigrations not working when Field takes FileSystemStorage parameter
-------------------------------------+-------------------------------------
Reporter: nliberg | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version:
Severity: Release blocker | 1.7-beta-1
Keywords: FileSystemStorage, | Resolution:
migrations | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by rajiv@…):
+1 on the excluding storage from FileField.deconstruct as chriscauley
proposes. This affects migrations with custom storages such as
S3BotoStorage from django-storages. Unless there is an expectation that
all storage backends will implement deconstruct (to no benefit from what I
can tell, as it does not actually affect the migration), it seems like an
unnecessary burden on updating projects.
--
Ticket URL: <https://code.djangoproject.com/ticket/22337#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.475d05fc0f43211276e3a1b1320401ee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
