Re: Django Docs for Forms - Alternative Pattern from Advanced Django Forms Usage talk?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Victor, On 10/22/2011 06:57 PM, Victor Hooi wrote: > /Disclaimer: This is about the the Django Docs, and a possible > suggestion for it - apologies if this isn't the correct group (but I > didn't think it quite fell into django-users). No

Django Docs for Forms - Alternative Pattern from Advanced Django Forms Usage talk?

heya, *Disclaimer: This is about the the Django Docs, and a possible suggestion for it - apologies if this isn't the correct group (but I didn't think it quite fell into django-users). * The official Django Docs for forms offers up the following pattern for Form view code: def

Re: The state of per-site/per-view middleware caching in Django

On Oct 21, 9:17 pm, Jim Dalton wrote: > On Oct 21, 2011, at 8:04 AM, Kääriäinen Anssi wrote: > > > I do not know nearly enough about caching to participate fully in this > > discussion. But it strikes me that the attempt to have CSRF protected > > anonymous page cached is

Re: i18n docs

On 22 oct. 2011, at 17:52, Carl Meyer wrote: > I'm an expert in neither internationalization nor localization, but I do > think that our code (in particular the highly user-visible bits like > settings) should use the same definitions as our docs, otherwise we're > just asking for confusion. And

Re: i18n docs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Aymeric, On 10/22/2011 05:02 AM, Aymeric Augustin wrote: > On IRC, Bas Peschier pointed out that the current docs follow the > "definitions" of i18n and l10n. > > In fact, the code (in particular the settings) uses the "gettext" > definitions

Re: i18n docs

Hello, On IRC, Bas Peschier pointed out that the current docs follow the "definitions" of i18n and l10n. In fact, the code (in particular the settings) uses the "gettext" definitions while the docs use the more general "Wikipedia" definition, and confusion ensues. For consistency, I think