Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #45937 > unrolled thread
| Started by | Carlos Nepomuceno <carlosnepomuceno@outlook.com> |
|---|---|
| First post | 2013-05-25 04:10 +0300 |
| Last post | 2013-05-25 04:10 +0300 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
RE: Ldap module and base64 oncoding Carlos Nepomuceno <carlosnepomuceno@outlook.com> - 2013-05-25 04:10 +0300
| From | Carlos Nepomuceno <carlosnepomuceno@outlook.com> |
|---|---|
| Date | 2013-05-25 04:10 +0300 |
| Subject | RE: Ldap module and base64 oncoding |
| Message-ID | <mailman.2095.1369444226.3114.python-list@python.org> |
Can you give an example of the code you have? ---------------------------------------- > From: jcasale@activenetwerx.com > To: python-list@python.org > Subject: Ldap module and base64 oncoding > Date: Fri, 24 May 2013 21:00:01 +0000 > > I have some data I am working with that is not being interpreted as a string requiring > base64 encoding when sent to the ldif module for output. > > The base64 string parsed is ZGV0XDMzMTB3YmJccGc= and the raw string is det\3310wbb\pg. > I'll admit my understanding of the handling requirements of non ascii data in 2.7 is weak > and as such I am failing at adjusting the regex that deduces is the string contains characters > requiring base64 encoding when being output. > > Any insight, or nudges in the right direction would be appreciated! > Thanks, > jlc > -- > http://mail.python.org/mailman/listinfo/python-list
Back to top | Article view | comp.lang.python
csiph-web