Re: Setting current timezone in Django 1.4, and middleware

I set up a fresh Django 1.4 project and adapted the middleware described in the docs; I stored the timezone on the user profile of two different users, and logged in as each of them in separate browsers, along with a third completely separate window (so I had three different sessions). It appear

Setting current timezone in Django 1.4, and middleware

In 1.4, what exactly is the scope of the current timezone? In other words, if I use activate() to set a current timezone, is that global? Or does it only apply to the current request (and not persist across requests)? Or, some other scope? (I looked at the source

Signals sent while running custom django-admin commands?

With Django 1.2.1 I'm finding that signals don't seem to get sent while running a custom manage.py command. Looking at the documentation[1], it looks like this may be the intended behavior; is the documentation saying that _only_ the post_syncdb signal gets sent when running django-admin commands,

Most-polished forum application?

would be a plus, but I can manage a manual migration if I have to. And an app that has an active community would be great.) Any thoughts? Thanks, peppergrower -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this

not required in Atom feeds

Question about Django's syndication framework: why does it require a link for each item/entry in a feed? As far as I can tell, this is optional in the Atom specification (http://www.atomenabled.org/ developers/syndication/atom-format-spec.php#element.link): >> The "atom:link" element defines a r

Re: Include multiple entries in Atom feed

at the raw XML generated by my feed.) On Sep 28, 9:17 pm, peppergrower wrote: > I've read Django's documentation on its syndication framework, and > it's mostly pretty thorough.  I set up an Atom feed that seems to work > just fine.  However, I'd like to include

Include multiple entries in Atom feed

I've read Django's documentation on its syndication framework, and it's mostly pretty thorough. I set up an Atom feed that seems to work just fine. However, I'd like to include the last several entries in my feed: how can I do this in Django? (I'm creating an Atom 1.0 feed, in case it matters.)

Re: Test tables not all created

By "normal database" I meant the one that gets used normally by Django, e.g., while running the development server (manage.py runserver)--in contrast to the test database. Thanks for the pointer. I checked my INSTALLED_APPS, and somehow I'd missed a module. I'm not sure how that happened, since

Test tables not all created

p://docs.djangoproject.com/en/dev/topics/testing/ , but didn't see anything that addresses this: it just blithely states that a test database will be created. I'm sure it's just something silly, but what could I be missing that would lead to missing test tables? peppergrower --~--~-