#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 Simon Charette):
As I've mentioned in
[https://github.com/django/django/pull/9617#issuecomment-360546339
#28748's PR] I feel like this should be the the correct behavior in a
Python 3 only code base and this was probably caused by an overlooked case
during the porting of the affected code bases from Python 2 to Python 3.
In other words, if you are passing binary data to an interface expecting
text you should expect bad things to happen -- Python 3 is stricter about
this concept and it's a good thing IMHO.
Now, this change should at least have been mentioned in the 2.0 release
notes. The fact it wasn't makes me think there might other instances
changed by #27795 related commits that might have introduced similar
''regressions''.
--
Ticket URL: <https://code.djangoproject.com/ticket/29086#comment:4>
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.03ef8443cdcc0d8215eb83855a1daffc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
