QuerySet.__or__ bug?

| o [, ] >>> This doesn't seem to be correct or behavior, based on what I'm seeing in the code. Is there something special I need to do when dealing with a ManyToMany, or is this a bug? Thanks, Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 signature.asc Description: Digital signature

Re: django and LDAP support

ing). I'll be posting it in a day or so once it's cleaned up a bit more. During OSCON I mentioned to Adrian that I'd be willing to work on one that would make it into django. LDAP is working great for me but we're not the highest demand environment, though I'd expe

Re: django and LDAP support

On Tue, Aug 01, 2006 at 12:08:25PM -0700, Scott Paul Robertson wrote: > I'm actually doing LDAP auth with something I wrote myself, which I feel > is a little more general than the mentioned code (not that I'm > opinionated or anything). I'll be posting it in a day or so

Re: django and LDAP support

rd. > I'll start on this tomorrow. Out of curiosity how common is this sort of setup? I've only seen a handful of LDAP implementations, and this is new to me. Thanks for the comments, Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgpTklkBRjQxO.pgp Description: PGP signature

Re: django and LDAP support

On Wed, Aug 09, 2006 at 10:22:24PM -0600, Scott Paul Robertson wrote: > > Also, in the ldap setup I deal with, you must bind to the server using > > a service account before attempting a bind with the user-supplied > > credentials. The process goes something like > > >

Re: django and LDAP support

On Thu, Aug 10, 2006 at 12:41:21PM -0600, Scott Paul Robertson wrote: > 2. An option that is a function that will be called to generate a bind > string for the user. This gives a lot of flexibility in allowing for a > large variety of pre-bind methods to occur, and gives a lot of >

Re: django and LDAP support

Ok, one last change to make it more 'pythonic'. Just a slight change to make using the pre-auth bind function easier. I think this finishes out the patch. If there are any other ideas or suggestions, please let me know. Scott (http://code.djangoproject.com/ticket/2507/) -- Scott Paul

Re: django and LDAP support

AP_SEARCH_FILTER) I think that gives you the functionality you want, and makes it a lot easier in general. I've submitted the updated patch. Let me know if there's anything else, Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 signature.asc Description: Digital signature

Re: django and LDAP support

at is a good point, if you have both backends working, this would present a problem. I'll go ahead and have it generate a random password in there instead. Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgpEw6dDODQuN.pgp Description: PGP signature

Re: multiple authentication and session keys

order, or optionally take a > backend to try and get the user from. > You also run into a problem if you change the authentication backends and don't clear out your cookie. Django will fail trying to authenticate with a now non-existent backend. I can grab the traceback if it's neede

Re: django and LDAP support

think leaving it in is a benefit. Anyhow, let me know if you have any thoughts, and I'll have the patch in tonight. Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 signature.asc Description: Digital signature

Re: django and LDAP support

On Mon, Aug 14, 2006 at 12:51:47PM -0600, Scott Paul Robertson wrote: > Anyhow, let me know if you have any thoughts, and I'll have the patch in > tonight. > Patch is in place. I'm aware of a trailing sentence in the doc string and a typo with get_user() in the doc string

Re: django and LDAP support

any other suggestions tomorrow if at all possible. If not I'll just work on it on Monday. Thanks, Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgpO3XATbjWs8.pgp Description: PGP signature

Re: Proposal: Forms and BoundForms

follow' attribute of ChangeManipulators, and making sure that I can put values back in easily to the BoundForm (or whatever it's called). Not too worried about this going away, but just want to make sure. Otherwise I really like the proposal so far, and I'll chime in and give a +1 to ha

Re: Re: Proposal: Forms and BoundForms

On Fri, Sep 15, 2006 at 09:25:37PM -0500, James Bennett wrote: > > On 9/15/06, Scott Paul Robertson <[EMAIL PROTECTED]> wrote: > > Inter-field dependency. For example: > > Most of this looks like it can be much more flexibly handled by the > already-available valida

Re: Newforms: seperating database and form logic

model as well, right? Should that go in somewhere more general than the Admin class? -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgpoklEwM93Nu.pgp Description: PGP signature

Re: django.contrib.formtools: High-level abstractions of common form tasks

sed the Python Cryptography Toolkit (http://www.amk.ca/python/code/crypto) a number of times, and have been pretty pleased with it. Thought you might like to know. -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgpWBB5zmTwv1.pgp Description: PGP signature

Re: Proposal: Named auth backends and backend specific profiles

ll_data argument, the validator will assume that username is > required. My initial thinking is that an attribute named > username_required or something similar could be checked on the backend > object. To indicate that username is *not* required, you'd just set > that attribute on your

Re: Proposal: Named auth backends and backend specific profiles

e information from LDAP was good enough for us. Now to get the level of integration you want, it sound like what the generic auth branch does. Have you looked into using the branch? In any case I'm interested to see what you've done and curious to see what you had to do to

Re: newforms: proposal ModelForm Baseclass for model related Forms

idgets is a breeze: EntryForm.fields['text'].widget = some.widget.class() You can still add clean methods after the fact by assigning functions to EntryForm.clean_title, ie: EntryForm.clean_title = lambda self: pass # do stuff -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgpFUDqZuIRBs.pgp Description: PGP signature

Sub-directory in django/contrib/auth for contributed auth backends.

-- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgp2X7WN1R2Xg.pgp Description: PGP signature

Subdirectories for documentation?

would make sense to have their own page that is a child to another primary page. Thanks, Scott -- Scott Paul Robertson http://spr.mahonri5.net GnuPG FingerPrint: 09ab 64b5 edc0 903e 93ce edb9 3bcc f8fb dc5d 7601 pgpggYe5mCach.pgp Description: PGP signature

wiki coordinator position

So I've been tossing this idea around in my head for a while now, and wanted to see what everyone thought of the idea. Basically I think the wiki could use someone to work on it as something akin to an editor. Jacob put it well when I mentioned this to him yesterday, that the wiki could use a "ga

Re: wiki coordinator position

On Tue, Jul 24, 2007 at 06:52:54PM -0500, Adrian Holovaty wrote: > > On 7/24/07, Scott Paul Robertson <[EMAIL PROTECTED]> wrote: > > [ Discusion about editor for development wiki pages... ] > > Since I'm throwing out the idea, I'm willing to do this. Is any