On 20/01/12 17:22, Tom Evans wrote: > The python bug is marked wont-fix. In our production code, we have > temporarily worked around it by forcing sessions to be encoded with > protocol 1 (binary) rather than protocol 2, by monkey patching > pickle.HIGHEST_PROTOCOL in settings.py. > > Do you think it is right to use pickle.HIGHEST_PROTOCOL to pickle > session objects on branches that still support python 2.5? Given the > known issues with Cookie.Morsel, 2.5 and pickling, should Django > auto-monkey-patch this when it detects python 2.5?
We have fixed this bug in trunk by fixing HttpResponse (which is probably much nicer than the proposed monkey patching): https://code.djangoproject.com/changeset/17200 This bug is not big enough to warrant fixing in 1.3.X, according to our policy, I'm afraid. Regards, Luke -- "Cross country skiing is great if you live in a small country." (Steven Wright) Luke Plant || http://lukeplant.me.uk/ -- You received this message because you are subscribed to the Google Groups "Django developers" 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 this group at http://groups.google.com/group/django-developers?hl=en.
