#23843: Test failures on Oracle/Python3
-------------------------------------+-------------------------------------
Reporter: shaib | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by shaib):
Replying to [comment:2 tchaumeny]:
> The patch above implements the workaround in
https://community.oracle.com/thread/2165039?start=0&tstart=0. It seems to
solve the problem (at least on my Oracle VM), although it's kind of
cumbersome. It might be better to just skip that on Oracle.
The fact that the patch works is good info for solving the bug, but the
patch itself cannot be accepted. We (well, aaugustin, mostly) made a
significant effort to remove this kind of vendor-specific code from the
test-suite, and we'd like to keep it as clean of it as possible. But more
importantly, the test failure represents a genuine problem; the patch,
essentially, offers a workaround by adding backend-specific cruft in user
code. That is sort-of acceptable as a workaround, not as a solution.
The thing I am most curious about is why this fails only on Python3; our
code should be sending exactly the same objects (in terms of
bytes/unicode) on Python2, but it works there.
--
Ticket URL: <https://code.djangoproject.com/ticket/23843#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.5be4f1262326cfa05015a66d06be1dac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
