kakwa 10747cff93 add some python 3 support in the LDAP and AD backends ... python-ldap talks in bytes, as the rest of ldapcherry talks in unicode utf-8: * everything passed to python-ldap must be converted to bytes * everything coming from python-ldap must be converted to unicode The previous statement was true for python-ldap < version 3.X. With versions > 3.0.0 and python 3, it gets tricky, some parts of python-ldap takes string, specially the filters/escaper. so we have now: *_byte_p2 (unicode -> bytes conversion for python 2) *_byte_p3 (unicode -> bytes conversion for python 3) *_byte_p23 (unicode -> bytes conversion for python AND 3)		2019-02-09 16:08:18 +01:00
..
backend	add some python 3 support in the LDAP and AD backends	2019-02-09 16:08:18 +01:00
ppolicy	fix some errors in unused code	2017-01-31 20:59:49 +01:00
__init__.py	better log+fix in conf checking + fix in ppolicy handler	2019-02-08 20:38:29 +01:00
attributes.py	pep8	2019-02-07 20:16:39 +01:00
cli.py	pep 8	2019-02-07 21:09:42 +01:00
exceptions.py	better log+fix in conf checking + fix in ppolicy handler	2019-02-08 20:38:29 +01:00
lclogging.py	pep8 compliance	2015-10-19 20:36:18 +02:00
pyyamlwrapper.py	pep8 compliance for ldapcherry/pyyamlwrapper.py	2015-07-11 23:15:40 +02:00
roles.py	pep8	2019-02-07 20:16:39 +01:00
version.py	put version in standalone file	2017-04-06 20:34:32 +02:00