#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 Jon Dufresne):
> It seems to me the current behavior is really bad for projects that are
upgrading, because there's no warning or error, just silent bad data.
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?)
This idea of warn/error when mixing bytes with text is actually built into
Python with the [https://docs.python.org/3/using/cmdline.html#cmdoption-b
`-b` and `-bb` options]. I've used it to great success in my project to
discover mishandling of bytes and text. I don't think Django needs to
duplicate this functionality, but maybe the release notes could be
modified to recommend using `-b` to help discover missed cases when
upgrading.
--
Ticket URL: <https://code.djangoproject.com/ticket/29086#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/072.4d96b6a58c5d1a9653307eace97be0b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
