#19221: Cache keys can't be integers
-------------------------------------+------------------------------------
     Reporter:  mhsparks             |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Core (Cache system)  |                  Version:  master
     Severity:  Release blocker      |               Resolution:
     Keywords:                       |             Triage Stage:  Accepted
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+------------------------------------
Changes (by russellm):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * severity:  Normal => Release blocker
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Since this is an apparent regression in behavior, I'm marking this as a
 release blocker.

 Whether this is an actual bug will depend on whether we've ever
 contractually guaranteed that a cache key can be any type. I'm not
 necessarily convinced that an integer *should* be allowed to be a cache
 key (other than the fact that historically, it's apparently been allowed).
 So - the resolution here might be documenting the type guarantee, rather
 than fixing the 'bug'.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19221#comment:1>
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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to