File: README.rst

package info (click to toggle)
ldif3 3.2.2-1
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 180 kB
  • ctags: 209
  • sloc: python: 605; makefile: 151
file content (49 lines) | stat: -rw-r--r-- 1,450 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
ldif3 - generate and parse LDIF data (see `RFC 2849`_).

This is a fork of the ``ldif`` module from `python-ldap`_ with python3/unicode
support. See the first entry in CHANGES.rst for a more complete list of
differences.

Usage
-----

Parse LDIF from a file (or ``BytesIO``)::

    from ldif3 import LDIFParser
    from pprint import pprint

    parser = LDIFParser(open('data.ldif', 'rb'))
    for dn, entry in parser.parse():
        print('got entry record: %s' % dn)
        pprint(record)


Write LDIF to a file (or ``BytesIO``)::

    from ldif3 import LDIFWriter

    writer = LDIFWriter(open('data.ldif', 'wb'))
    writer.unparse('mail=alice@example.com', {
        'cn': ['Alice Alison'],
        'mail': ['alice@example.com'],
        'objectclass': ['top', 'person'],
    })

Unicode support
---------------

The stream object that is passed to parser or writer must be an ascii byte
stream.

The spec allows to include arbitrary data in base64 encoding or via URL. There
is no way of knowing the encoding of this data. To handle this, there are two
modes:

By default, the ``LDIFParser`` will try to interpret all values as UTF-8 and
leave only the ones that fail to decode as bytes. But you can also pass an
``encoding`` of ``None`` to the constructor, in which case the parser will not
try to do any conversion and return bytes directly.


.. _RFC 2849: https://tools.ietf.org/html/rfc2849
.. _python-ldap: http://www.python-ldap.org/