#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 Mariusz Felisiak):
> Should we submit a patch meant to be backported to 3.2 and 4.0 in
setUpTestData that solely deals with this particular edge case of models
and queryset with a BinaryField on Postgres to circumvent #27813?
Yes, it should be feasible by juggling with `__getstate__()/__reduce__()`
hooks 🤔 I think we should treat this as a release blocker because
`BinaryField` is built-in into Django and
3cf80d3fcf7446afdde16a2be515c423f720e54d broke previously working tests.
> What if we get other reports of users who ignored the deprecation
warning for other non-pickleable objects assigned during setUpTestData?
That would not be a release blocker, IMO, unless any other built-in is
non-pickleable.
--
Ticket URL: <https://code.djangoproject.com/ticket/33333#comment:9>
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.588a83f97dd0a6730f4bad0830c261e7%40djangoproject.com.
