[python-ldap] importing ldap changes my server paths

Michael Ströder michael at stroeder.com
Thu Jun 6 10:02:05 CEST 2013


D S wrote:
> I am using Django, and as soon as I import the ldap library (without making
> any actual use of the library), my server becomes useless.  Django depends
> on a file called urls.py to route server requests as they are received, and
> as soon as I import ldap, all incoming requests become 404, as if the
> server no longer knows where this routing file is.  Looking in ldap's
> __init__.py didn't reveal any obvious directory overwriting, etc.  If you
> are familiar with this library, can you give me a hint as to what is
> happening?  I have definitely narrowed it down to the import of this
> library, though.

I know python-ldap very well but I don't know anything about Django.

But I can't imagine how "import ldap" itself affects any Django mechanisms. I
suspect there's something wrong within your Django app.

Ciao, Michael.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2398 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.python.org/pipermail/python-ldap/attachments/20130606/8a2eb585/attachment.bin>


More information about the python-ldap mailing list