Hi Klaas,
Le mardi 12 juin 2012 13:13:14 UTC+2, Klaas van Schelven a écrit :
>
> 1] Migration of non-UTC to UTC: is there any script / best practice
> available?
>
Django's documentation mentions that all data should be converted to UTC
> when switching to USE_TZ=True. See:
> https://docs.djan
Le jeudi 21 juin 2012 13:36:53 UTC+2, Aymeric Augustin a écrit :
>
> I haven't written that script and I don't know anyone else who has. No
> promises, but since you need it, I may find the motivation to write it.
>
Here you go: https://gist.github.com/2971450
The script
Le mardi 22 mai 2012 02:57:05 UTC+2, Arthur a écrit :
>
> I recently upgraded one of my machines to Django 1.4 to patch a bug
> related to the use of PostGIS 9.1. I read the documentation on the new
> support for time zones and added USE_TZ=True to my settings.py file.
> Nonetheless, when I atte
Le dimanche 13 mai 2012 04:33:33 UTC+2, James Zheng a écrit :
>
> has anyone else run into the problem below?
Hi James,
Since you're talking about USE_TZ, I suppose you're using Django 1.4. But
the code you're quoting no longer exists in that version:
https://github.com/django/django/commit/9b1
Le mardi 31 juillet 2012 22:34:46 UTC+2, Tejinder Singh a écrit :
>
> Django 1.4 does not store aware times for TimeField, it only does for
> DateTimeField. Its really annoying, as python datetime.time object does
> support TZINFO just like datetime.datetime objects. I wonder if it is a
> bug? B
Le lundi 3 septembre 2012 02:48:24 UTC+2, dalupus a écrit :
>
> On the item list screen however the datetime is not formated and seems
> to be in utc format like so:
> 2012-09-03 00:28:21.664176+00:00
> so it appears it is not adjusting to display the field in the users
> timezone.
>
> Any ide
Hi folks,
We've scheduled maintenance operations on djangoproject.com tomorrow, starting
at 09:00 UTC.
The website and the docs may be temporarily unavailable.
Please use the mirror of the docs at Read The Docs in the meantime:
http://django.readthedocs.org/
Thanks,
--
Aymeric.
--
You r
Hi Michael,
>
> *Django 1.5:*
>
>- The database-level auto-commit is turned OFF.
>
> Yes.
>
>- SQL standards dictate that every query opens a transaction if one
>does not already exist. This happens regardless of the database's
>auto-commit setting.
>
> Yes, this is required
Hello,
I just upgraded the Django Debug Toolbar to support Django 1.5 and Python
3. Since there hasn't been a release in a long time, and since support for
Python 3 required rather extensive changes, I would really appreciate if
you could try it before we make an official release on PyPI in a f
Hello,
I'm happy to annonce that we're almost ready to release version 1.0 of the
Debug Toolbar! Now we need your help to try the beta:
https://github.com/django-debug-toolbar/django-debug-toolbar/releases/tag/1.0-beta
The documentation is available on Read the Docs — make sure you read the
"la
On 16 déc. 2013, at 12:33, kamagatos wrote:
> we should start thinking about a way to catch and display every ajax/json
> responses. because more and more applications are becoming ajax ready and
> they use front-end frameworks like angularjs or backbone to deal with getting
> stuff on the bac
Hello,
I just released 1.0 final. Enjoy!
--
Aymeric.
Le dimanche 15 décembre 2013 14:11:50 UTC+1, Aymeric Augustin a écrit :
>
> Hello,
>
> I'm happy to annonce that we're almost ready to release version 1.0 of the
> Debug Toolbar! Now we need your help to try the bet
It's a bug in PyYAML: https://code.djangoproject.com/ticket/18867
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegr
13 matches
Mail list logo
