#27753: Cleanups when no supported version of Django supports Python 2 anymore
--------------------------------------+------------------------------------
Reporter: Aymeric Augustin | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* cc: Jon Dufresne (added)
Comment:
My PRs address everything in this ticket except `DjangoUnicodeDecodeError`
-- I'm not sure about the rationale for removing it as it still may
provide some value:
`DjangoUnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in
position 0: invalid start byte. You passed in b'\xff' (<class 'bytes'>)`
vs. `UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position
0: invalid start byte`.
Could you explain your thinking, Jon? Maybe the mistake leading to this
exception (#5640) isn't common enough in Python 3 to continue with the
special handling?
--
Ticket URL: <https://code.djangoproject.com/ticket/27753#comment:22>
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/067.aa7c0d980f870e9649038041e14a95b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
