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
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
|
%global _empty_manifest_terminate_build 0
Name: python-heptapod
Version: 4.1.0
Release: 1
Summary: Heptapod server-side Mercurial hooks, extension, etc.
License: GPLv2+
URL: https://foss.heptapod.net/heptapod/py-heptapod
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/3b/ac/1a0d63617d6f23d51df784bd009207b079df2321c98c9e1515010a80ee35/heptapod-4.1.0.tar.gz
BuildArch: noarch
%description
# Python components of the Heptapod server
[](https://foss.heptapod.net/heptapod/py-heptapod/commits/branch/default)
[](https://foss.heptapod.net/heptapod/py-heptapod/commits/branch/default)
[Heptapod](https://heptapod.net) is the friendly fork of GitLab that brings
Mercurial compatibility in. It is a system with multiple components, involving
several programmation languages, notably Ruby, Go and Python.
The purpose of this package is to centralize all Heptapod Python code that is
not (yet) in any other, more generic Python project (Mercurial, its extensions,
general-purpose libraries…), and keep them in a high state of quality.
## Scope and versioning policy
This Python project is not meant for anything else than being a component of
the Heptapod **server**, nor is it the whole of Heptapod, only
the parts that happen to be written in Python.
The interdependency with other Heptapod components is very tight, to the point
that the requirements file of Heptapod releases usually completely pins this
project. Starting with version
1.0.0 (for Heptapod 0.17), we are planning to follow
[semver](https://semver.org) rules (with PEP 440 for development versions).
Python 3 is fully supported since version 0.13.0, tested with 3.7 and 3.8.
[Python 2 support is deprecated](https://foss.heptapod.net/heptapod/heptapod/-/issues/353) as of version 1.0.0. Only the
`testhelpers` subpackage is fully supported for both Python versions,
because it can be used for more general Mercurial related testing.
Python 2 support will be dropped entirely when we will have a new home for
`testhelpers`.
## Development guide
### Launching the tests
We have unit and integration tests with `pytest`, they'd be typically
run in a virtualenv:
```
python 3 -m venv venv
source venv/bin/activate
./run-all-tests
```
We have a 100% coverage policy, that is enforced by `run-all-tests` and
therefore by the continuous integration.
This full run takes about 20 seconds in our continuous integration, and
usually less than that on developer workstations.
### Workflow rules
We follow the Heptapod default workflow. Please make a topic, and submit a
Merge Request.
Merge Request Pipelines have to pass, and coverage to stay at 100% for the MR
to be technically acceptable – we can help achieving these results, it's not
mandatory for submitting MRs and gather some feedback.
## Contents
### WSGI serving of repositories
Provided by `heptapod.wsgi` (not fully independent yet)
### Mercurial Hooks
`heptapod.hooks.check_publish.check_publish`:
permission rules about public changesets in pushes.
`heptapod.hooks.git_sync.mirror`:
synchronisation to inner auxiliary Git repository for exposition to GitLab
`heptapod.hooks.dev_util`: useful hooks for debug and development
### Mercurial extension
The `heptapod` extension will provide specific commands and generally everything
that should be done with full access to Mercurial internals.
%package -n python3-heptapod
Summary: Heptapod server-side Mercurial hooks, extension, etc.
Provides: python-heptapod
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-heptapod
# Python components of the Heptapod server
[](https://foss.heptapod.net/heptapod/py-heptapod/commits/branch/default)
[](https://foss.heptapod.net/heptapod/py-heptapod/commits/branch/default)
[Heptapod](https://heptapod.net) is the friendly fork of GitLab that brings
Mercurial compatibility in. It is a system with multiple components, involving
several programmation languages, notably Ruby, Go and Python.
The purpose of this package is to centralize all Heptapod Python code that is
not (yet) in any other, more generic Python project (Mercurial, its extensions,
general-purpose libraries…), and keep them in a high state of quality.
## Scope and versioning policy
This Python project is not meant for anything else than being a component of
the Heptapod **server**, nor is it the whole of Heptapod, only
the parts that happen to be written in Python.
The interdependency with other Heptapod components is very tight, to the point
that the requirements file of Heptapod releases usually completely pins this
project. Starting with version
1.0.0 (for Heptapod 0.17), we are planning to follow
[semver](https://semver.org) rules (with PEP 440 for development versions).
Python 3 is fully supported since version 0.13.0, tested with 3.7 and 3.8.
[Python 2 support is deprecated](https://foss.heptapod.net/heptapod/heptapod/-/issues/353) as of version 1.0.0. Only the
`testhelpers` subpackage is fully supported for both Python versions,
because it can be used for more general Mercurial related testing.
Python 2 support will be dropped entirely when we will have a new home for
`testhelpers`.
## Development guide
### Launching the tests
We have unit and integration tests with `pytest`, they'd be typically
run in a virtualenv:
```
python 3 -m venv venv
source venv/bin/activate
./run-all-tests
```
We have a 100% coverage policy, that is enforced by `run-all-tests` and
therefore by the continuous integration.
This full run takes about 20 seconds in our continuous integration, and
usually less than that on developer workstations.
### Workflow rules
We follow the Heptapod default workflow. Please make a topic, and submit a
Merge Request.
Merge Request Pipelines have to pass, and coverage to stay at 100% for the MR
to be technically acceptable – we can help achieving these results, it's not
mandatory for submitting MRs and gather some feedback.
## Contents
### WSGI serving of repositories
Provided by `heptapod.wsgi` (not fully independent yet)
### Mercurial Hooks
`heptapod.hooks.check_publish.check_publish`:
permission rules about public changesets in pushes.
`heptapod.hooks.git_sync.mirror`:
synchronisation to inner auxiliary Git repository for exposition to GitLab
`heptapod.hooks.dev_util`: useful hooks for debug and development
### Mercurial extension
The `heptapod` extension will provide specific commands and generally everything
that should be done with full access to Mercurial internals.
%package help
Summary: Development documents and examples for heptapod
Provides: python3-heptapod-doc
%description help
# Python components of the Heptapod server
[](https://foss.heptapod.net/heptapod/py-heptapod/commits/branch/default)
[](https://foss.heptapod.net/heptapod/py-heptapod/commits/branch/default)
[Heptapod](https://heptapod.net) is the friendly fork of GitLab that brings
Mercurial compatibility in. It is a system with multiple components, involving
several programmation languages, notably Ruby, Go and Python.
The purpose of this package is to centralize all Heptapod Python code that is
not (yet) in any other, more generic Python project (Mercurial, its extensions,
general-purpose libraries…), and keep them in a high state of quality.
## Scope and versioning policy
This Python project is not meant for anything else than being a component of
the Heptapod **server**, nor is it the whole of Heptapod, only
the parts that happen to be written in Python.
The interdependency with other Heptapod components is very tight, to the point
that the requirements file of Heptapod releases usually completely pins this
project. Starting with version
1.0.0 (for Heptapod 0.17), we are planning to follow
[semver](https://semver.org) rules (with PEP 440 for development versions).
Python 3 is fully supported since version 0.13.0, tested with 3.7 and 3.8.
[Python 2 support is deprecated](https://foss.heptapod.net/heptapod/heptapod/-/issues/353) as of version 1.0.0. Only the
`testhelpers` subpackage is fully supported for both Python versions,
because it can be used for more general Mercurial related testing.
Python 2 support will be dropped entirely when we will have a new home for
`testhelpers`.
## Development guide
### Launching the tests
We have unit and integration tests with `pytest`, they'd be typically
run in a virtualenv:
```
python 3 -m venv venv
source venv/bin/activate
./run-all-tests
```
We have a 100% coverage policy, that is enforced by `run-all-tests` and
therefore by the continuous integration.
This full run takes about 20 seconds in our continuous integration, and
usually less than that on developer workstations.
### Workflow rules
We follow the Heptapod default workflow. Please make a topic, and submit a
Merge Request.
Merge Request Pipelines have to pass, and coverage to stay at 100% for the MR
to be technically acceptable – we can help achieving these results, it's not
mandatory for submitting MRs and gather some feedback.
## Contents
### WSGI serving of repositories
Provided by `heptapod.wsgi` (not fully independent yet)
### Mercurial Hooks
`heptapod.hooks.check_publish.check_publish`:
permission rules about public changesets in pushes.
`heptapod.hooks.git_sync.mirror`:
synchronisation to inner auxiliary Git repository for exposition to GitLab
`heptapod.hooks.dev_util`: useful hooks for debug and development
### Mercurial extension
The `heptapod` extension will provide specific commands and generally everything
that should be done with full access to Mercurial internals.
%prep
%autosetup -n heptapod-4.1.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-heptapod -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue May 30 2023 Python_Bot <Python_Bot@openeuler.org> - 4.1.0-1
- Package Spec generated
|
