#18348 closed New feature (fixed)
Make parts of the sessions API public
Reported by: | Aymeric Augustin | Owned by: | Preetham Nosum |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | vpnosum@… | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Many developers attempt to use session.session_key
. Documenting it would help them use it correctly.
Related thread: https://groups.google.com/group/django-developers/browse_thread/thread/d78e268f8b15fd9d
Updated documentation, pull request here: https://github.com/django/django/pull/6952
Change History (8)
comment:1 by , 12 years ago
comment:2 by , 12 years ago
#19147 is another example of a developer attempting to access session_key
before saving the session.
comment:3 by , 12 years ago
Triage Stage: | Design decision needed → Accepted |
---|
comment:4 by , 11 years ago
Component: | contrib.sessions → Documentation |
---|
comment:5 by , 8 years ago
Cc: | added |
---|---|
Description: | modified (diff) |
Has patch: | set |
Owner: | changed from | to
Status: | new → assigned |
Note:
See TracTickets
for help on using tickets.
We should probably include
create()
andsave()
in the public API. See #18344.