#29086: Bytestrings on CharFields getting saved as "b'data'"
-------------------------------------+-------------------------------------
Reporter: Collin Anderson | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Release blocker | 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 Collin Anderson):
"Django no longer accepts bytestrings in certain code paths"
"Python 3 is stricter about this concept and it's a good thing IMHO." -
Right, it raises an error when you pass bytes, it seems to me Django
should do the same thing.
It seems to me the current behavior is really bad for projects that are
upgrading. Maybe the force_text() calls (#27795) need to be
bytes_not_allowed() or something. (Too late to raise an error for 2.0, but
maybe we could start raising a warning?)
--
Ticket URL: <https://code.djangoproject.com/ticket/29086#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/072.58842ca1421e5577cec80bb0705ed58f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
