In Python, you need a blank __init__.py in the directory containing
the module. Otherwise, Python won't consider it a place where the
backends.py can live.
One of the things currently in progress for 1.6 (and it will be in the
upcoming alpha) is much improved support for custom auth modules.
They'll be easier to install and to configure, and will otherwise act
just like the built-in auth modules (LDAP, NIS, AD) in that they'll
show up in the module list and can have configuration forms. I'll post
to the reviewboard-...@googlegroups.com list when this is ready and
the docs are written.
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Fri, Dec 3, 2010 at 4:27 PM, Eric Johnson
> Eliding some details:
> In Apache config, I changed:
> PythonPath "['/usr/local/scripts/reviewboard', '/var/www/path/to/conf'] +
> And in the settings, I set the custom auth module to
> And then I've got a folder
> ... and backends.py has a modified LDAP authentication with name
> When I run that, I get an error:
> No module named "custom.backends".
> The Python Path shown in the error message clearly shows
> '/usr/local/scripts/reviewboard' in the path.
> I can't figure out why Django doesn't see my backends.py file. Any tips?
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at