#16378: locmem should use pickle.HIGHEST_PROTOCOL to match memcached et. al.
------------------------------------+-------------------------------------
               Reporter:  PaulM     |          Owner:  nobody
                   Type:  Bug       |         Status:  new
              Milestone:  1.4       |      Component:  Core (Cache system)
                Version:  SVN       |       Severity:  Normal
             Resolution:            |       Keywords:
           Triage Stage:  Accepted  |      Has patch:  0
    Needs documentation:  0         |    Needs tests:  0
Patch needs improvement:  0         |  Easy pickings:  1
                  UI/UX:  0         |
------------------------------------+-------------------------------------
Changes (by PaulM):

 * stage:  Unreviewed => Accepted


Comment:

 @adamnelson: Changing a ticket from Accepted to Unreviewed isn't usually
 done unless the original acceptance was grossly wrong.

 I agree with the expansion of the scope - Django should use
 pickle.HIGHEST_PROTOCOL everywhere it uses pickle.

 The reason this ticket was opened re: locmem and dbcache was not about
 performance, but consistency. In the current configuration, it's possible
 to have code that works just fine in testing with locmem that mysteriously
 stops working in production on memcached.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/16378#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 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to