Opened 14 years ago
Closed 13 years ago
#15945 closed Cleanup/optimization (fixed)
Thread locals note
| Reported by: | sorl | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.3 |
| Severity: | Normal | Keywords: | |
| Cc: | sorl | Triage Stage: | Design decision needed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The page http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser
inaccurately describes the solution as a (huge) security risk, read more:
http://groups.google.com/group/django-users/browse_thread/thread/e7af359d7d183e04
Change History (9)
comment:1 by , 14 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
follow-up: 4 comment:2 by , 14 years ago
| Cc: | added |
|---|
Who manages the wiki? A comment on what to do with opinions on its contents would be helpful.
comment:4 by , 14 years ago
Replying to sorl:
Who manages the wiki? A comment on what to do with opinions on its contents would be helpful.
Anybody can edit the wiki. If you think something needs to change in any of its pages, feel free to do so ;)
comment:6 by , 14 years ago
Yes, it looks like it's locked. Apparently it's not the first time: #13207.
comment:7 by , 14 years ago
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
There's no good reason for this page to be locked. I'm reopening so that someone with admin access to the Django wiki removes that lock.
comment:8 by , 14 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
Hm, in that case I defer to ubernostrum and/or russellm who edited that page in the past.
comment:9 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
| UI/UX: | unset |
Since Django has, for years, supported a much simpler way to accomplish the things people wanted that for, I've simply deleted the wiki page.
The wiki isn't part of Django's official documentation.