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
|
This package is maintained with git-buildpackage(1). It follows DEP-14 for
branch naming (e.g. using debian/master for the current version in Debian
unstable due Debian Python team policy).
It uses pristine-tar(1) to store enough information in git to generate bit
identical tarballs when building the package without having downloaded an
upstream tarball first.
When working with patches it is recommended to use "gbp pq import" to import
the patches, modify the source and then use "gbp pq export --commit" to commit
the modifications.
The changelog is generated using "gbp dch" so if you submit any changes don't
bother to add changelog entries but rather provide a nice git commit message
that can then end up in the changelog.
It is recommended to build the package with pbuilder using:
gbp buildpackage --git-pbuilder
For information on how to set up a pbuilder environment see the git-pbuilder(1)
manpage. In short:
DIST=sid git-pbuilder create
gbp clone https://salsa.debian.org/python-team/packages/pytest-asyncmy.git
cd pytest-asyncmy
gbp buildpackage --git-pbuilder
pytest-asyncmy for Debian
=========================
Upstream is using poetry as build backend, this isn't working nicely at the
moment as dh-python isn't able to build the wheel and finally the Python
package.
We 'switched' to use the classical 'python3 setup.py' approach to create the
needed data for the binary package for the moment. But like to switch back to
use poetry once we figured out how we can build the package with this backend
correctly.
The main issue is the not working step of 'python3 -m build ...' for creating
the wheel. The wheel is needed to have included the compiled C bindings which
should get triggered by calling the script 'build.py', but this isn't working
for no. And before the file setup.py needs to get created, this isn't also not
working.
--- %< pyproject.toml ---
...
[tool.poetry.build]
generate-setup-file = true
script = "build.py" <----
[build-system]
build-backend = "poetry.core.masonry.api"
requires = ["poetry-core", "setuptools", "cython"]
...
--- >% ----
As a compensation we build the package by using a classical call of
'python3 setup.py ...'.
-- Carsten Schoenert <c.schoenert@t-online.de> Sun, 13 Oct 2024 11:20:00 +0100
|
