#18852: Backwards-incompatible change in django.core.signing
---------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: master
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by aaugustin):
I agree about avoiding bytestrings when possible. At the lower level,
crypto operates on bytes. The question is, where we draw the frontier?
My proposal moves it back "upwards" a bit — above the `b64_decode/encode`
functions.
It is easier to read (and makes less changes) if you also take into
account your previous commit. I'm attaching an aggregated diff that shows
the net result.
--
Ticket URL: <https://code.djangoproject.com/ticket/18852#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
