#19221: Check that cache keys are string
-------------------------------------+------------------------------------
Reporter: mhsparks | Owner: nobody
Type: Bug | Status: new
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by carljm):
I agree that implicitly converting `42` and `"42"` to be the same cache
key is bad, and we should migrate away from it with an appropriate
deprecation path. (I think the patch to do so should take some care to
"assume string and only do more work if that assumption fails" rather than
"check pre-emptively", in order to preserve all possible speed in the
common case.)
--
Ticket URL: <https://code.djangoproject.com/ticket/19221#comment:12>
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].
For more options, visit https://groups.google.com/groups/opt_out.
