#28121: force_text incorrectly handles SafeBytes under PY3
------------------------------------+--------------------------------------
Reporter: Thomas Achtemichuk | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Comment (by Thomas Achtemichuk):
Also, there is this, fairly explicit comment in `force_text` that makes me
believe that the behavior under PY3 is wrong:
{{{
# Note: We use .decode() here, instead of six.text_type(s,
encoding,
# errors), so that if s is a SafeBytes, it ends up being a
# SafeText at the end.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28121#comment:6>
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.dd66c5181e74347b8fba936d1145ac97%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
