Hi all One of our sites was recently upgraded to 1.4 and now some previously working code is failing.
The code tries to access and utilize the session id from the user, but if it tries to do this on the request the session is created on, the session id is None. The equivalent session object in 1.3 always presents a valid session id. 1.3.1: >>> import django >>> from django.http import HttpRequest >>> from django.conf import settings >>> from django.utils.importlib import import_module >>> >>> engine = import_module(settings.SESSION_ENGINE) >>> req = HttpRequest() >>> req.session = engine.SessionStore(None) >>> print django.VERSION (1, 3, 1, 'final', 0) >>> print req.session.session_key a8b409a6b29ac5a59022350445f8bfa4 1.4: >>> import django >>> from django.http import HttpRequest >>> from django.conf import settings >>> from django.utils.importlib import import_module >>> >>> engine = import_module(settings.SESSION_ENGINE) >>> req = HttpRequest() >>> req.session = engine.SessionStore(None) >>> print django.VERSION (1, 4, 0, 'final', 0) >>> print req.session.session_key None This is using the DB backend, but perusing the changes to contrib.session, I think all backends will be similarly affected. So, is the session key being available part of the API, or is relying on the session key existing incorrect? Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
