#33333: Models with a BinaryField fail to deepcopy in setUpTestData() on
PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: Adam Zimmerman | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Given we're pretty close to the 4.0 release date I'm not against including
a limited hack for `setUpTestData` that special cases `Model` and
`QuerySet` instances.
It does feel weird that we're treating this as a release blocker now
thought given it has been broken since `BinaryField` was introduced and
`setUpTestData`
[https://github.com/django/django/commit/3cf80d3fcf7446afdde16a2be515c423f720e54d
#diff-
7833da5b45a68d00834388d97dd5c4413e3796497c7bc5e0cc2621b08a2d0df1R1108-R1120
has been emitting deprecation warnings about it since Django 3.2].
--
Ticket URL: <https://code.djangoproject.com/ticket/33333#comment:6>
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/063.ccd0279f153063194cbdef5b5c0a7939%40djangoproject.com.
