#21954: 1.7a1 - Migration syntax error
---------------------------------+---------------------------------------
Reporter: caulagi | Owner:
Type: Bug | Status: new
Component: Migrations | Version: 1.7-alpha-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+---------------------------------------
Comment (by loic84):
@russellm, I get your point.
We need to make a decision at how much whitelisting we want to make in
`MigrationWriter` since each supported `type` is special-cased, we don't
for instance support things like `frozenset`.
The case of "memberships start Jan 1 2014, unless otherwise specified."
can already be addressed by providing a `callable` that returns such date.
--
Ticket URL: <https://code.djangoproject.com/ticket/21954#comment:5>
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.4e6882886c4cbf942a6359b70d4b3e78%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
