Opened 8 years ago

Closed 8 years ago

#13207 closed (fixed)


Reported by: Beuc Owned by: nobody
Component: * Version:
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


AFAICS 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/ :)

Change History (3)

comment:1 Changed 8 years ago by James Bennett

Resolution: wontfix
Status: newclosed

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.

comment:2 Changed 8 years ago by Beuc

Resolution: wontfix
Status: closedreopened

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.

comment:3 Changed 8 years ago by Russell Keith-Magee

Resolution: fixed
Status: reopenedclosed


Note: See TracTickets for help on using tickets.
Back to Top