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
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
|
%global _empty_manifest_terminate_build 0
Name: python-ldif
Version: 4.2.0
Release: 1
Summary: generate and parse LDIF data (see RFC 2849).
License: BSD
URL: https://github.com/abilian/ldif
Source0: https://mirrors.aliyun.com/pypi/web/packages/c1/04/2db7fb27b3f98dba07f744b50a2496da8aad3f09edee5c98cc07a75b71c5/ldif-4.2.0.tar.gz
BuildArch: noarch
Requires: python3-pip
%description
# ldif - parse and generate LDIF data (see [RFC 2849](https://tools.ietf.org/html/rfc2849)).
This is a fork of the `ldif` module from
[python-ldap](http://www.python-ldap.org/) with python3/unicode support.
One of its benefits is that it's a pure-python package (you don't
depend on the `libldap2-dev` (or similar) package that needs to be
installed on your laptop / test machine / production server).
See the last entry in [changelog](https://github.com/abilian/ldif/blob/main/CHANGES.rst) for a more complete list of
differences.
This package only support Python 3 (\>= 3.7, actually).
## Usage
Parse LDIF from a file (or `BytesIO`):
```python
from ldif import LDIFParser
from pprint import pprint
parser = LDIFParser(open("data.ldif", "rb"))
for dn, record in parser.parse():
print('got entry record: %s' % dn)
pprint(record)
```
Write LDIF to a file (or `BytesIO`):
```python
from ldif 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.
%package -n python3-ldif
Summary: generate and parse LDIF data (see RFC 2849).
Provides: python-ldif
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-ldif
# ldif - parse and generate LDIF data (see [RFC 2849](https://tools.ietf.org/html/rfc2849)).
This is a fork of the `ldif` module from
[python-ldap](http://www.python-ldap.org/) with python3/unicode support.
One of its benefits is that it's a pure-python package (you don't
depend on the `libldap2-dev` (or similar) package that needs to be
installed on your laptop / test machine / production server).
See the last entry in [changelog](https://github.com/abilian/ldif/blob/main/CHANGES.rst) for a more complete list of
differences.
This package only support Python 3 (\>= 3.7, actually).
## Usage
Parse LDIF from a file (or `BytesIO`):
```python
from ldif import LDIFParser
from pprint import pprint
parser = LDIFParser(open("data.ldif", "rb"))
for dn, record in parser.parse():
print('got entry record: %s' % dn)
pprint(record)
```
Write LDIF to a file (or `BytesIO`):
```python
from ldif 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.
%package help
Summary: Development documents and examples for ldif
Provides: python3-ldif-doc
%description help
# ldif - parse and generate LDIF data (see [RFC 2849](https://tools.ietf.org/html/rfc2849)).
This is a fork of the `ldif` module from
[python-ldap](http://www.python-ldap.org/) with python3/unicode support.
One of its benefits is that it's a pure-python package (you don't
depend on the `libldap2-dev` (or similar) package that needs to be
installed on your laptop / test machine / production server).
See the last entry in [changelog](https://github.com/abilian/ldif/blob/main/CHANGES.rst) for a more complete list of
differences.
This package only support Python 3 (\>= 3.7, actually).
## Usage
Parse LDIF from a file (or `BytesIO`):
```python
from ldif import LDIFParser
from pprint import pprint
parser = LDIFParser(open("data.ldif", "rb"))
for dn, record in parser.parse():
print('got entry record: %s' % dn)
pprint(record)
```
Write LDIF to a file (or `BytesIO`):
```python
from ldif 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.
%prep
%autosetup -n ldif-4.2.0
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-ldif -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri Jun 09 2023 Python_Bot <Python_Bot@openeuler.org> - 4.2.0-1
- Package Spec generated
|
