#27795: Audit force_text invocations
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: Claude
Type: | Paroz
Cleanup/optimization | Status: assigned
Component: Utilities | Version: master
Severity: Normal | 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 Tim Graham <timograham@…>):
In [changeset:"b39aabc6c6b84cbe4005f3fdf3b9c0c4307afc76" b39aabc]:
{{{
#!CommitTicketReference repository=""
revision="b39aabc6c6b84cbe4005f3fdf3b9c0c4307afc76"
Refs #27795 -- Reworked get_or_create test erroneously mixing bytes and
str.
As CharField.to_python() now always calls str(), assigning bytes to a
CharField is no longer correct usage. Doing so results in a warning:
django/db/models/fields/__init__.py:1061: BytesWarning: str() on a bytes
instance
Use a unique constraint violation to trigger the database error instead.
Warning introduced in 301de774c21d055e9e5a7073e5bffdb52bc71079.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27795#comment:8>
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/065.dfee0083022fb3ffdf40136c5f764dd2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
