Opened 15 years ago
Closed 14 years ago
#13207 closed (fixed)
Unlock http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser
| Reported by: | Beuc | Owned by: | nobody |
|---|---|---|---|
| Component: | *.djangoproject.com | Version: | |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
AFAICS http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser was locked after its last edit, without precising a reason in the edit log. That last edit removed most of the text.
The removed text documents a technique that I think is legitimate in some situations (such as webforms), and that is also used in Django to store the current locale (e.g. in utils/translations/trans_real.py) :)
Change History (3)
comment:1 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
Would you like to elaborate some more about that on the wiki page, and explain in what context it's ok to use the thread-locals approach (such as in Django i18n)?
Education is good.
Note:
See TracTickets
for help on using tickets.
The page was trimmed because the "solution" it presented has a large number of issues which make it a terrible approach to the problem. The page was locked because a large number of people apparently would prefer an immediate copy-and-paste wrong solution to a proper solution which involves a bit more study, time and effort.