#22351: New django migrations and places where lambdas are supposed
--------------------------------------+------------------------------------
Reporter: dimyur27@… | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: migrations lambdas | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by chriscauley):
I tried to reproduce this specific issue and I don't get any error when
running `python manage.py makemigrations APP_NAME` with a lambda in
limit_choices_to. That kwarg is not returned in
`ForeignKey.deconstruct()`, so the migration inspector doesn't care if it
is a lambda. Can you show me code to illustrate what you mean?
--
Ticket URL: <https://code.djangoproject.com/ticket/22351#comment:3>
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/076.56a79e74bb705fadc973ce2b3234c7e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
