#13227: Query cloning fails with models having Lock as instance member
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: nobody
Type: | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* ui_ux: => 0
* easy: => 0
Comment:
In [changeset:"1dd96f731df3ca9df0e3ff83a9a8e723dc7e8685" 1dd96f73]:
{{{
#!CommitTicketReference repository=""
revision="1dd96f731df3ca9df0e3ff83a9a8e723dc7e8685"
Refs #13227 -- Adjusted a test to avoid making a shared test model
unpickable.
This allowed the Note model to be used in setUpTestData() which requires
assigned model instances to be copy.deepcopy()'able.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/13227#comment:12>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bb793b537b45d454f6692202bf287f6a%40djangoproject.com.
