Re: More multi-database plumbing (WAS Re: Changing DatabaseWrapper._cursor() to take a dict instead of settings)

2009-03-12 Thread Alex Gaynor
On Fri, Mar 13, 2009 at 12:26 AM, Adrian Holovaty wrote: > > On Thu, Mar 12, 2009 at 11:53 PM, Alex Gaynor > wrote: > > Great, since we've moved so quickly on improving our plumbing for this > there > > was one other idea I wanted to put forth(since I

More multi-database plumbing (WAS Re: Changing DatabaseWrapper._cursor() to take a dict instead of settings)

2009-03-12 Thread Adrian Holovaty
On Thu, Mar 12, 2009 at 11:53 PM, Alex Gaynor wrote: > Great, since we've moved so quickly on improving our plumbing for this there > was one other idea I wanted to put forth(since I believe it needs to happen > for any multidb implementation).  In terms of plumbing the

Re: Changing DatabaseWrapper._cursor() to take a dict instead of settings

2009-03-12 Thread Alex Gaynor
On Thu, Mar 12, 2009 at 11:42 PM, Adrian Holovaty wrote: > > On Thu, Mar 12, 2009 at 7:59 PM, Alex Gaynor > wrote: > >> I've created a ticket here: > >> > >>http://code.djangoproject.com/ticket/10487 > >> > >> If anybody (Alex?) wants to code up a

Re: guidelines for docs/misc/distributions.txt

2009-03-12 Thread Tim Graham
I've created the following ticket to address the issue along with an initial patch: http://code.djangoproject.com/ticket/10424 The new page for distribution specific installation instructions can be found: http://code.djangoproject.com/wiki/Distributions Hope that helps, Tim On Mar 5, 7:40 am,

Re: Changing DatabaseWrapper._cursor() to take a dict instead of settings

2009-03-12 Thread Alex Gaynor
On Thu, Mar 12, 2009 at 7:04 PM, Adrian Holovaty wrote: > > On Wed, Mar 11, 2009 at 11:39 PM, Yuri Baburov wrote: > > Maybe let's go a bit further towards pool of db connections and wrap a > > bunch of lines importing backend into some function that

Re: Changing DatabaseWrapper._cursor() to take a dict instead of settings

2009-03-12 Thread Adrian Holovaty
On Wed, Mar 11, 2009 at 11:39 PM, Yuri Baburov wrote: > Maybe let's go a bit further towards pool of db connections and wrap a > bunch of lines importing backend into some function that depends on > engine argument? > And later call it with settings.DATABASE_ENGINE to import

Re: Changing DatabaseWrapper._cursor() to take a dict instead of settings

2009-03-12 Thread Alex Gaynor
On Thu, Mar 12, 2009 at 1:26 PM, Yuri Baburov wrote: > > On Thu, Mar 12, 2009 at 11:44 AM, James Bennett > wrote: > > > > On Wed, Mar 11, 2009 at 11:39 PM, Yuri Baburov > wrote: > >> Maybe let's go a bit further towards pool of db

Re: Changing DatabaseWrapper._cursor() to take a dict instead of settings

2009-03-12 Thread Yuri Baburov
On Thu, Mar 12, 2009 at 11:44 AM, James Bennett wrote: > > On Wed, Mar 11, 2009 at 11:39 PM, Yuri Baburov wrote: >> Maybe let's go a bit further towards pool of db connections and wrap a >> bunch of lines importing backend into some function that

Re: Call for review: #689 - REMOTE_USER authentication

2009-03-12 Thread Jacob Kaplan-Moss
Hey Gary -- Looks good to me. My only comment would be that I'd move the docs into howto/ instead of topics/. Other than that, I'm happy with this code as is. Malcolm's pickier than I am, though, so you might want to see what he's got to say :P Jacob

Re: Unified access to response.context in test client (follow-up)

2009-03-12 Thread Julien Phalip
On Mar 12, 11:10 pm, Russell Keith-Magee wrote: > On Thu, Mar 12, 2009 at 8:31 PM, Julien Phalip wrote: > > > On Mar 12, 9:30 pm, Russell Keith-Magee > > wrote: > >> On Thu, Mar 12, 2009 at 7:20 PM, Julien Phalip

Re: Unified access to response.context in test client (follow-up)

2009-03-12 Thread Russell Keith-Magee
On Thu, Mar 12, 2009 at 8:31 PM, Julien Phalip wrote: > > On Mar 12, 9:30 pm, Russell Keith-Magee > wrote: >> On Thu, Mar 12, 2009 at 7:20 PM, Julien Phalip wrote: >> >> > Hi, >> >> > A few months ago James raised the issue on this

Re: Unified access to response.context in test client (follow-up)

2009-03-12 Thread Julien Phalip
On Mar 12, 9:30 pm, Russell Keith-Magee wrote: > On Thu, Mar 12, 2009 at 7:20 PM, Julien Phalip wrote: > > > Hi, > > > A few months ago James raised the issue on this list: > >http://groups.google.com/group/django-developers/browse_thread/thread... > >

Re: Unified access to response.context in test client (follow-up)

2009-03-12 Thread Russell Keith-Magee
On Thu, Mar 12, 2009 at 7:20 PM, Julien Phalip wrote: > > Hi, > > A few months ago James raised the issue on this list: > http://groups.google.com/group/django-developers/browse_thread/thread/1b10084ea969141e > > Basically, the type for the test client's response context is >

Unified access to response.context in test client (follow-up)

2009-03-12 Thread Julien Phalip
Hi, A few months ago James raised the issue on this list: http://groups.google.com/group/django-developers/browse_thread/thread/1b10084ea969141e Basically, the type for the test client's response context is inconsistent. Sometimes it's a dictionary and other times it's a list of dictionaries,

Re: Call for review: #689 - REMOTE_USER authentication

2009-03-12 Thread Malcolm Tredinnick
Hey Gary, On Thu, 2009-03-12 at 01:40 -0500, Gary Wilson Jr. wrote: > Just posted an updated patch: > > http://code.djangoproject.com/attachment/ticket/689/689.4.diff If nobody gets to it beforehand, I'll give this a serious look tomorrow. Cheers, Malcolm

Call for review: #689 - REMOTE_USER authentication

2009-03-12 Thread Gary Wilson Jr.
Just posted an updated patch: http://code.djangoproject.com/attachment/ticket/689/689.4.diff Gary --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to