> Well.. how about you tell me whether you're going to pursue the
> project before I spend a bunch of time giving feedback when you don't
> actually want it?
>
> As a top sheet summary - To be brutally honest, I'm still not
> convinced you've got a coherent plan that would be acceptable to
> Djang
> Like I said originally - this is a big, hard problem. It's definitely
> a problem worth solving, but because it's a difficult problem, it's
> going to be a lot harder to convince us that you're the right person
> for the job.
>
So any comments or suggestions to my answers in the last post?
I do
On Mar 26, 8:34 am, Russell Keith-Magee
wrote:
> On Fri, Mar 26, 2010 at 3:22 AM, d3f3nd3r wrote:
>
> > On Mar 25, 4:19 pm, Russell Keith-Magee
> > wrote:
>
> >> Firstly, Backwards compatibility. contrib.auth is a major component in
> >> many, if not
On Mar 26, 8:34 am, Russell Keith-Magee
wrote:
> On Fri, Mar 26, 2010 at 3:22 AM, d3f3nd3r wrote:
>
> > On Mar 25, 4:19 pm, Russell Keith-Magee
> > wrote:
>
> >> Firstly, Backwards compatibility. contrib.auth is a major component in
> >> many, if not
ggest one (used
by the Austrian hackerspace metalab (http://metalab.at)) and a lot of
smaller ones)
I faced some limitations of the auth framework when I tried to write a
custom auth backend for Django on Google App Engine (http://
bitbucket.org/d3f3nd3r/djangoappengine-helpers/). The problem was,
On Mar 25, 4:19 pm, Russell Keith-Magee
wrote:
>
> First up, this is probably the most ambitious project on the proposal
> list. When I warn that this is a tough issue, I'm not kidding. This is
> gonna be *hard*. With a capital Huh. There are all sorts of technical
> issues, and a couple of poli
ot of smaller ones)
I faced some limitations of the auth framework when I tried to write a
custom
auth backend for Django on Google App Engine (http://bitbucket.org/
d3f3nd3r/djangoappengine-helpers/). The problem was, that
the auth framework forces you to call a login() function when the
user logs i
