2011/9/6 Paul McMillan :
>> I'm going to use the same trick used by USE_L10N and explained by Anssi: set
>> USE_TZ to False in global_settings.py and to True in the template of
>> settings.py. This preserves backwards compatibility but the new code is the
>> default for new projects.
>
> This is
Good morning,
I have been using Drupal for a while now, but am slowly moving toward
DJango.
I am currently working on quite an ambitious project, which I will be
releasing under a permissive license (New BSD or better).
I would like my project to be as accessible as possible. To this end,
I woul
thanx let me check it out
On Tue, Sep 6, 2011 at 5:43 PM, Silvan Spross wrote:
> i think this will help:
>
> https://docs.djangoproject.com/en/dev/ref/contrib/csrf/#how-to-use-it
> *
> *
>
> *allink.*creative
>
>
On Sep 6, 10:47 pm, Aymeric Augustin
wrote:
> Under PostgreSQL, I assume I have to use a TIMESTAMP WITH TIME ZONE and set
> the connection's timezone to UTC if I want non-Django applications using the
> same database to obtain correct results, regardless of their connection's
> timezone. To be
On Tue, Sep 6, 2011 at 6:29 PM, Alec Taylor wrote:
> Good morning,
>
> I have been using Drupal for a while now, but am slowly moving toward
> DJango.
>
> I am currently working on quite an ambitious project, which I will be
> releasing under a permissive license (New BSD or better).
>
> I would
Hi,
Documentation states that IPs within 'INTERNAL_IPS' will:
- See debug comments, when DEBUG is True.
To my eyes, that means that unless the IP is in there, they won't see the
debug comments/page.
However, the debug page is still shown to the user when DEBUG is on, even if
they are not in the
On Wed, Sep 7, 2011 at 7:08 PM, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
>
>
> On Tue, Sep 6, 2011 at 6:29 PM, Alec Taylor wrote:
>
>> Good morning,
>>
>> I have been using Drupal for a while now, but am slowly moving toward
>> DJango.
>>
>> I am currently
I just wanted to chime in with a couple of extra notes here. I won't
comment on most of it as I think it's all spot on :)
On Sep 3, 10:40 pm, Aymeric Augustin
wrote:
> Django should use timezone-aware UTC datetimes internally
> .
>
> Example
At first sorry for my English :).
LANGUAGE_CODE setting doesn't work correctly.
When I configured LANGUAGE_CODE="mn", but default language code is
"en".
from django.utils.translation import get_language
print get_language()
>>> en
I think it has been done on purpose, and should not be changed.
Because different authentication backends may choose to support
inactive users or not. And the default (ModelBackend) supports
inactive users which is expressed in
ModelBackend.supports_inactive_user = True. So I would suggest you
writ
10 matches
Mail list logo