#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 Claude Paroz):
Simon, your diagnostic might be right, but I think it's late in the 4.0
release cycle to make such changes now, also considering changing
`memoryview` to `bytes` might have serious memory implications not plainly
visible in tests.
What about writing a workaround for `setuptestData` in 4.0, and make a
more proper and thorough fix in 4.1?
--
Ticket URL: <https://code.djangoproject.com/ticket/33333#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.23c4081b625dd448dbb5c20b78a4079b%40djangoproject.com.
