#33216: Use simplified paths for deconstruct of expressions
------------------------------------------------+------------------------
               Reporter:  Adam Johnson          |          Owner:  nobody
                   Type:  Cleanup/optimization  |         Status:  new
              Component:  Migrations            |        Version:  dev
               Severity:  Normal                |       Keywords:
           Triage Stage:  Unreviewed            |      Has patch:  0
    Needs documentation:  0                     |    Needs tests:  0
Patch needs improvement:  0                     |  Easy pickings:  0
                  UI/UX:  0                     |
------------------------------------------------+------------------------
 Previously `F()` deconstructed to: `django.db.models.expressions.F()`. But
 since it can also be imported from `django.db.models`,
 [https://github.com/django/django/pull/14047 PR #14047] changed it to
 deconstruct to `django.db.models.F()`. This simplifies generated migration
 code where it will be referenced only as `from django.db import models /
 models.F()`.

 As Mariusz pointed out on the PR, the same technique can be applied to
 other expressions, further simplifying generated migrations.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/33216>
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.cb9befe30ec67e4a04c4052b3d548209%40djangoproject.com.

Reply via email to