Thanks for filing the bug. It's probably best to discuss higher-level stuff on the mailing list, and details of the ticket on the ticket. That said, there's a lot of overlap.
While setting pickle to use a lower protocol would "fix" the problem, it's really only a bandaid. Lower versions of the pickle protocol are badly inefficient with new-style classes, and should be avoided at all costs. We really just need to stop trying to pickle a class that is unpicklable. The appropriate fix for this probably lies in serializing the SimpleCookie object back into a string (that's what cookies are anyway, right?) before we pass it to pickle. I haven't looked closely at the code there, but that's where I would start. As for the test, you probably want to test it more holistically - maybe a test that fetches a page in the test client several times in a row and makes sure that it is the same each time. Further discussion should probably happen on the ticket. -Paul -- 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.
