#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:6 tchaumeny]:
> After some investigation, that seems to be a bug in cx_Oracle, which
handles unicode objects differently between different versions — this
isn't due to Django as the failure is reproductible using cx_Oracle cursor
directly. I opened an issue there
https://bitbucket.org/anthony_tuininga/cx_oracle/issue/6/python-3-string-
parameters-are-not-handled with more detail.
Hey @tchaumeny, great work. I am swamped with non-Django issues at the
moment, so will only be able to look deeper into this later this week, but
your research looks sound and identifying the problem is more than half
way to solving it; so I just wanted to say cheers.
--
Ticket URL: <https://code.djangoproject.com/ticket/23843#comment:7>
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.b8815d6280d2c3a5214043d5d6ce9adb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
