Hi Aymeric,
Thanks for the answers!
I've decided to postpone the migration on one of our bigger projects
to USE_TZ = True until after I have some experience with proper time
zone handling in a greenfield project. This won't last forever,
though, and once I get to it I'll report back with any glob
Hi all,
I have a number of questions on Django 1.4's Time Zones.
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.djangoproject.com/en/dev/top
Phil,
A quick reply so I may be wrong on the details.
I think you're running into a limitation on the standard way of doing
things in Django.
I've talked about this before here:
http://groups.google.com/group/django-users/browse_thread/thread/22875fd287d0aa81/d6cf04a857424678?show_docid=d6cf04a85
Hi all,
I just ran into the same problem. Locally it doesn't occur, but it
does on the server.
I share Karen's analysis that the variable path of type unicode cannot
be encoded into ascii.
However, sys.getfilesystemencoding is also "UTF-8", so I don't see why
os.stat would try to encode using asc
>
> Sure. However, Djangocon 2010 finished a week ago, so you're going to
> have to wait until next year before we have the next serious
> opportunity to do this.
>
http://djangocon.eu/ is going to be in the spring of 2011. Let's see
how many of the "best of the bunch" are going to make it to
Amst
On Sep 23, 2:01 am, Russell Keith-Magee
wrote:
> On Wed, Sep 22, 2010 at 11:31 PM, Klaas van Schelven
>
> wrote:
> >> I'm yet to see a genuine case of (a) -- every time I've seen (a), it's
> >> really masked version of (b), (c) or (d).
>
> > I
Ok, it actually turns out the above idea works. That is to say, with a
minimal amount of weird tricks (an empty models.py, plugging in some
app_labels in the right places).
Of course: without the tricks it would be even better.
http://bitbucket.org/vanschelven/extendible_app_experiment
A few note
> I'm yet to see a genuine case of (a) -- every time I've seen (a), it's
> really masked version of (b), (c) or (d).
I disagree. I think there are very specific problems, that has not
been adressed by any of the responses above.
Let's focus on one for now: how to extend models in any given app.
A
Shawn: thanks
Just started watching the video and I'm noticing my complaints are not
unique.
> Wow! I guess your definition of an app and expectation of re-usuability
> from an app written by someone else
> is fairly high!
Actually, a big part of the problem is reusing my own apps. Mostly
since
9 matches
Mail list logo
