Re: A more robust conditional get

2007-10-21 Thread Ivan Sagalaev
Malcolm Tredinnick wrote: > So, as an addition to the current behaviour, I'm probably +1 on > including this. There's a bit of common stuff we can factor out from > that code to avoid duplication with the middleware and other ETag > handling code people might want to write, but that's minor stuff.

Re: #2539 - Namespacing template tags and libraries

2007-10-21 Thread [EMAIL PROTECTED]
On Oct 21, 5:40 pm, "Andrew Durdin" <[EMAIL PROTECTED]> wrote: > Tick #2539 "Custom tags and filters can be restricted by namespace" > was one of the ones I was going to pick up during the django sprint, > but someone else beat me to it. However, the other day I noticed that > the patch against

#2539 - Namespacing template tags and libraries

2007-10-21 Thread Andrew Durdin
Tick #2539 "Custom tags and filters can be restricted by namespace" was one of the ones I was going to pick up during the django sprint, but someone else beat me to it. However, the other day I noticed that the patch against it was old, and admitted to be incomplete by its author. Since namespac

Re: PostgreSQL 8.3 and asynchronous commits

2007-10-21 Thread Jacob Kaplan-Moss
On 10/21/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > This sounds quite tasty: > http://developer.postgresql.org/pgdocs/postgres/wal-async-commit.html > > I'd like to add support for that. In reality, async. commit is something you'd turn on in your postgresql.conf and just leave on; there isn

Re: psycopg (both 1 and 2) may drop support for multiple interpreters (used by mod_python and mod_wsgi)

2007-10-21 Thread Malcolm Tredinnick
Hi Graham (and Jeremy, who originally started the thread), On Sun, 2007-10-21 at 11:55 +, Graham Dumpleton wrote: > They have now committed changes in relation to this: > > http://www.initd.org/tracker/psycopg/changeset/902 > > On visual inspection the changes look to do what I was sugges

Re: psycopg (both 1 and 2) may drop support for multiple interpreters (used by mod_python and mod_wsgi)

2007-10-21 Thread Graham Dumpleton
They have now committed changes in relation to this: http://www.initd.org/tracker/psycopg/changeset/902 On visual inspection the changes look to do what I was suggesting. Note that the changes do mean there is a penalty for when psycopg is used in anything but first interpreter created by Pyt

PostgreSQL 8.3 and asynchronous commits

2007-10-21 Thread Jeremy Dunck
This sounds quite tasty: http://developer.postgresql.org/pgdocs/postgres/wal-async-commit.html I'd like to add support for that. Obviously only for postgres and 8.3, but perhaps with a setting to turn it on or off depending on the site's needs? I think trying to implement or modify a transactio