Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #46075
| From | Michael Ströder <michael@stroeder.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: Ldap module and base64 oncoding |
| Date | 2013-05-26 17:16 +0200 |
| Organization | A noiseless patient Spider |
| Message-ID | <knt8of$flb$1@dont-email.me> (permalink) |
| References | <BLU176-W6DFF254921D99D8816B74D7940@phx.gbl> <mailman.2138.1369496613.3114.python-list@python.org> |
Joseph L. Casale wrote: >> Can you give an example of the code you have? > > I actually just overrode the regex used by the method in the LDIFWriter class to be far more broad > about what it interprets as a safe string. Are you sure that you fully understood RFC 2849 before doing this? Which version of python-ldap are you using? > I really need to properly handle reading, manipulating and > writing non ascii data to solve this... Module ldif in python-ldap does that for you based on RFC 2849. Without seeing your code using it I cannot tell what's wrong. > Shame there is no ldap module (with the ldifwriter) in Python 3. 1. The module ldif is stand-alone. So you could easily make it available for Python 3. 2. "Shame" is the wrong term here. Personally I currently have no requirement to use Python 3 and I'm quite busy with other things. So contributors are welcome. But they should be willing to do some serious work giving continous support - not only a half-baken patch. Ciao, Michael.
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
RE: Ldap module and base64 oncoding "Joseph L. Casale" <jcasale@activenetwerx.com> - 2013-05-25 15:42 +0000 Re: Ldap module and base64 oncoding Michael Ströder <michael@stroeder.com> - 2013-05-26 17:16 +0200
csiph-web