#36899: Implement `Session.__bool__`
-------------------------------------+-------------------------------------
     Reporter:  Jake Howard          |                     Type:
                                     |  Cleanup/optimization
       Status:  new                  |                Component:
                                     |  contrib.sessions
      Version:  6.0                  |                 Severity:  Normal
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
 It's often useful to check whether the user has a session, for example to
 avoid creating one unnecessarily. Since `request.session` is always
 populated when `SessionMiddleware` is used, it's better to check whether
 the session is empty.

 #36898 documents `Session.is_empty()` which achieves this, but it could
 also be nice if `Session` supported a boolean check directly through
 `__bool__`, which would just call `is_empty` internally.

 This would mean `if request.session` works as expected. The downside being
 `if getattr(request, "session", None)` would be `False` when sessions are
 being used, but the session is empty (arguably `hasattr` would be better
 there anyway).
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36899>
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/django-updates/0107019c1f1d0a27-eb640b01-9f21-4d0e-8310-33ca113a7968-000000%40eu-central-1.amazonses.com.

Reply via email to