#28188: Field._get_default() prevents model fields from being pickled
-------------------------------------+-------------------------------------
     Reporter:  Adam Alton           |                    Owner:  GitHub
                                     |  <noreply@…>
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  1.11
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  fixed
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"74b0837bef6270a78f55878c488561f81a6339f7" 74b0837]:
 {{{
 #!CommitTicketReference repository=""
 revision="74b0837bef6270a78f55878c488561f81a6339f7"
 [1.11.x] Fixed #28188 -- Fixed crash when pickling model fields.

 Regression in d2a26c1a90e837777dabdf3d67ceec4d2a70fb86.

 Thanks Adam Alton for the report and test, and Adam Johnson for
 suggesting the fix.

 Backport of a9874d48b1b9d91988b9f299726ec4f559fb2f75 from master
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/28188#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/067.a713c0c60864abee87c8df0fa998570f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to