#29331: Model fields where the field name is shadowed by Python property aren't
     Reporter:  Ben Mathes           |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  2.0
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:
     Keywords:  models,              |             Triage Stage:  Accepted
  deferred_field, save               |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
Changes (by Tim Graham):

 * needs_tests:  1 => 0
 * stage:  Unreviewed => Accepted


 That's interesting, I didn't know about the `name` argument to `Field`. Is
 it documented? The last issue I found for it was #14695.

 I'm not sure if this can be fixed. Do you plan to offer a patch? If not, I
 suppose the restriction could at least be documented.

Ticket URL: <https://code.djangoproject.com/ticket/29331#comment:4>
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 
For more options, visit https://groups.google.com/d/optout.

Reply via email to